|
|
|
Performance is mainly about response time, which is, given a certain action, the amount of time it takes to get a reaction or result. It is important that the action is completed quickly. More importantly, the user must be given information about what is going on until the action is completed. Performance must always be ensured.
List views and databases can grow to several hundred entries and this needs to be taken into account when designing and implementing.
Note that the time limits given in the sections below are recommendations. Factors such as reference hardware, emulator program, running processes, number of application entries, amount of data etc can influence application start time.
When a specific task requires a long time to complete the user must be informed about the progress. For example, in the case of deleting multiple entries, update the progress notification regularly by indicating how many entries have been processed so far.
If a task takes seconds to complete the user must be given information about the progress of the task.
If a task requires a long time to complete, the user must be given the option to cancel the task. The application must then understand that the operation was cancelled and not completed.
If a task takes seconds to complete the user must be able to cancel the operation.
When improving application performance, focus should be on tasks that are run frequently. This kind of performance improvement will also help save battery power as “clever algorithms” require less energy.
Tasks that are performed very often, several times a day, must be optimized as much as possible.
Recommended maximum time for deleting 100 entries: 4 seconds.