Revision history [back]

I often have the occurence that a process/app that needs some time to start up makes the Device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing a indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy running his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar like the volume indicator that roghly progresses with percentage of time until the app is usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

I often have the occurence that a process/app that needs some time to start up makes the Device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing a an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy running starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar like the volume indicator that roghly progresses with percentage of time until the app is usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

I often have the occurence that a process/app that needs some time to start up makes the Device device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar like the volume indicator that roghly progresses with percentage of time until the app is usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

I often have the occurence that a process/app that needs some time to start up makes the device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar (maybe even one bar per upstarting process) like the volume indicator that roghly progresses with percentage of time until the app is app/process is actually usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

I often have the occurence that a process/app that needs some time to start up makes the device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar (maybe even one bar per upstarting process) like the volume indicator that roghly progresses with percentage of time until the app/process is actually usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

I often have the occurence that a process/app that needs some time to start up makes the device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar (maybe even one bar per upstarting process) like the volume indicator that roghly progresses with percentage of time until the app/process is actually usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!

UPDATE: the initial request was an indicator at all as it was not recognized by the OP that there actually is one - so the request is no was changed to have the indication more recognizable

I often have the occurence that a process/app that needs some time to start up makes the device feel unresponsive and laggy. Away from subjective perception, this behaviour sometime leeds me to initiate double commands or even forgeting that i startet something and initiating a different command, whichs process is then sometimes started faster than the first command action, but is pushed to background once the heavy process finally fully started.

This could be solved by showing an indicator that the device is "busy" (i know its not fully busy, but for the users perception it should be thought of as busy starting his command) or more open "starting your command xyz".

As we do not have a mousepointer to have an indicator analog to desktop OSes, i suggest to display a top bar (maybe even one bar per upstarting process) like the volume indicator that roghly progresses with percentage of time until the app/process is actually usable. Maybe even have a visual effect in the screen area the user pointed at to initiate his command, like dimming or pulsing an area until his command is fully executed.

I hope my genglish is understandable and i did not create a double post. Cheers!