[EDITOR'S NOTE] This list is out of date with the release of version 2.0.0. We are working on replacing this with an easier to maintain version of our working to-do/wish list, and to incorporate a voting system. Until that is in place, use it to check and see if the feature you are wanting is already here. If not, or to add your vote for a feature that is already on the list, drop us an email or leave a comment in the Wish List forum.

We have replaced the previous list that appeared here with the current Wish List.

You might automatically assume that the length of the wish list indicates that TimeLogger is lacking a lot of important features. Take a look at the features and screen shots on the TimeLogger information page, and you'll see that this is not the case - it is already a feature-rich application. The length of our Wish List shows that we are listening to our customers.

TimeLogger has been well-received by many people, and many have left us feedback indicating features they would like to see. We have rejected a very few that have gone against the purpose of the application, or we feel that they would complicate the interface unnecessarily for a feature that would be of limited utility for the majority of our users. For the most part, we have taken the suggestions (and added a few of our own) and compiled the following list. These are in no particular order, although we have added our notes about each if we have some idea about the order of importance that should be placed on them. Please provide your feedback if you feel that a higher priority should be placed on any of these items than what we seem to have assigned. User feedback has always (and will always) take precedence of our preconceived notions of importance!

Items in bold are those that we are considering as the highest priority for our next major release.

1. We have one major feature idea that we are not releasing to the public because we want to be the first to roll it out. It is unfortunately not technically possible with the current Developer Tools from Apple, but we feel that the capabilities that we need will exist in a future version of Apple's tools, and we have already submitted a feature request to them.
2. If a user switches to/from 12/24 hour format existing entries that were recorded in the other format do not appear correctly. Time difference calculations remain in-tact, but the displayed start and stop times appear incorrect or not at all. We consider this a bug, but not one that we feel needs to be addressed urgently because very few users switch between 12 and 24 hour time format frequently. It will definitely be fixed in the next relase (either major or minor release). (fixed in iPod/iPhone OS version 3.0)
3. Their is a bug in Apple's "UIDatePicker" that affects people who use 12 hour time format (primarily users in the USA). The bug makes it so that, if a picker defaults to a time before noon, if you scroll ahead the hour column only to 12, the AM/PM selector correctly moves to "PM," but the time recorded scrolls back to AM (midnight instead of noon). We have reported this bug to Apple, including code to prove the bug, and expect for them to provide a fix. Apple has acknowledged to us that this is a known bug in the current developer tools/code. If they do not provide a fix in the near future, we will figure out an appropriate workaround. In the meantime, of you are affected by this bug, instead of rolling only the hour column forward, either roll the minute column forward, and then the hour column, or roll the AM/PM selector forward first, and then roll the hour selector backward to 12.
4. On the "Stop Timers" screen, display more properties of started timers. This option will be more appropriate when the ability to tie started timers to Categories, Clients and Jobs happens before the "Stop Timer" stage, and we plan to implement it then (probably in our next major release - 1.3.0 or 2.0.0).
5. Show a total of hours accumulated for all started timers on the "Stop Timers" screen.
6. The ability to pause and resume a timer, allowing users to resume that timer when a task continues. Being fundamentally different than the (initial) intended use of TimeLogger, this presents some interface challenges. This has been our number one requested feature enhancement, so we are definitely on the path to figuring out a good solution for it, and you should expect to see it in a future release
7. The ability to remove a stop time on a stopped timer. This would have the effect of restarting a timer (as though it had not been stopped. This is closely related to pausing a timer, so we would expect to roll it out at the same time
8. The ability to "copy" a timer's data as a new timer. In other words, copy a timer's Category, Client, Job and Notes, but select a new start time. This would be very handy for people who tend to work on the same or similar tasks throughout the day. This is similar to being to remove a stop time on a started timer, so we would plan to carry it out at the same time as that feature (as well as the ability to pause timers).
9. The ability to deduct fixed intervals from a timed period. For example, "subtract 1 hour for lunch" so that users would not have to stop a timer and start another. This is sort of an "after-the-fact" version of the ability to pause timers.
10. Default settings to automatically apply a deduction to times that span a certain period. For example, "by default, always deduct 60 minutes from any time record that begins before Noon and ends after 1 PM."
11. Integration with third party/online invoicing applications. Their hasn't been as much demand for this as we had anticipated, so it has taken a back-burner. The feedback that we have received indicates that most of these applications can accept CSV input, so the CSV options that we have provided have been sufficient. If we are to resume talks of this option, we would like to know which third party applications y'all would like to see.
12. Configuration options that supply default Categories, Clients and Jobs, so people who are working on mostly one Category, Client or Job for long periods of time can specify which of those options they desire to auto-fill when they stop a timer (added in version 1.3.0)
13. Specification of input requirements. In other words, adding configuration options that allow users to specify which items (Categories, Clients, Jobs or Notes) have to be supplied before allowing them to stop a timer.
14. A free/lite version. Our thought would be to have a version that only stores data for 30 days and would not include backup/recovery options or CSV email capabilities. Users would still be able to send plain text email reports, and all other options would remain in-place. Do you think that this would provide enough of an "evaluation" of the program to help users decide whether they would want to bump up to the full version?
15. A configuration option that allows users to disable the auto-correct feature of the iPhone/iPod Touch for this application only. (added in version 1.3.0)
16. International/language support. Which language(s) would you like to see first?
17. Desktop backup and recovery capabilities. This is something that we'd like to implement relatively soon, but we haven't been able to come up with any good interface ideas that would not require for us to build a separate desktop application. We don't really want to be in the desktop application market, but something like a Java application may be feasible. Although it may be the technically simplest solution for us to implement, we don't necessarily want to go to the extent of creating a web interface on the iPhone/iPod that users could access from their desktop because we feel that the interface for such a tool will be too confusing for the average user of the application. what do you think?
18. Manual time entry. That is, the ability to specify something like "5 hours" instead of specific start and stop timers. Again, this is fundamentally different than the initial intent of TimeLogger, but we have received enough requests for it that we feel strongly that we need to implement the feature. The challenge for us is going to be implementing the interface in a way that does not confuse the existing structure. Ideas?
19. The ability to setup work-weeks and overtime rates. These items tie closely into cost/billing calculations as well as manual time entry, so they are likely to sit on hold until those features are implemented. Once again, this is contrary to the intent of TimeLogger, so the interface will be a challenge for us, but we feel that it will fit nicely into the "manual time entry" feature.
20. The ability to specify flat fees for a job so that time logged to it determines the hourly rate. This will be implemented at the same time as cost/billing rates.
21. Add a second notes field. Given its limited utility to many users, this would be implemented as an option that can be toggled on and off for those who need it. See the next item...
22. The ability to toggle on and off fields that are displayed in the iPhone/iPod Touch interface, and the ability to hide fields in generated reports. This is conducive to direct invoicing from the mobile device, so this is likely to be implemented with other invoicing features.
23. Be able to tie Jobs to "All Clients." Some folks have jobs with descriptions that belong to all (or most) of their clients. We'll plan to get this worked into a near-future update.
24. The ability to specify Categories, Clients, Jobs and Notes immediately when starting a timer rather than waiting until stopping the timer. This can be carried out in one of two ways. Without boring you on the first, which we're not likely to implement even though it would be easiest to program, we will tell you how we plan to carry this out. Our currently desired method will be clean from an interface standpoint. We will add configuration options so that users can choose to include any, all or none of Categories, Clients, Jobs and Notes on the "Start Timer" screen. This will enable any user to make the "Start Timer" screen contain exactly the information that he or she wants to set when starting a timer. We expect to have this in our next major release (either 1.3.0 or 2.0.0) (added in version 1.3.0)
25. The ability to specify the name of the person who is working on a job/task, and the ability to narrow reports by person. Again, given its limited utility to the majority of our users, this will be a configuration option that users will be able to enable/disable.
26. Automatically stop timers when another has started. This is another feature that would require a configuration option since many users desire to keep more than one timer running at the same time. This is also something that makes more sense when users may specify other data about the timer when they start a timer (as opposed to when they stop a timer, as it currently behaves), so this would be implemented at the same time as the ability to specify other data immediately when starting a timer.
27. Create PDF reports and/or invoices from the device and send them via email. This is something that is likely to tie into the invoicing feature, and our current hunch is that we would simply follow the format of a default invoice from QuickBooks. This feature would be tied into the Address Book (Contacts application), enabling you to choose a client from a list and have that client's information appear in the invoice header. Any thoughts on that?
28. Add a configuration option that, when a user stops a timer, would enable a prompt (a Yes or No selection) asking the user if he/she would like to start a new timer that starts at the same time the current entry was stopped. This would go hand-in-hand with the ability to stop other timers when a new one is started (actually, this is sort of the opposite approach to the same result), and would likely be made available at the same time. Question: It seems to us that this is a more common/logical way to think about how to make starting and stopping timers at the same point in time easier for people. Should we consider this to be a replacement to item 25 above, or would enough people think of this task in the way it is described in item 25 that having both methods would have value?
29. The ability to sort the Current Entries screen in descending order (newest entries first).(added in version 1.3.2)
30. Add loading indicators prior to entering any screen that takes more than approximately one-half of a second to load when it is fully populated with data. This will provide positive feedback to the user so that he/she is not wondering for that short time if his/her action was recognized. This will not add any perceivable time to what is required to load any given screen, but should improve the user experience. Added to version 1.2.1
31. A more compact view of the "Current Entries" screen." Since each user will have a different perspective of exactly how this should look, we want to come up with a way to allow users to organize the contents of this screen. Some thought will need to go into how to implement this without mucking up the interface. We're open to suggestions.
32. The ability to store voice recordings with time entries in addition to typed notes. Expect to see this!
33. The ability to change the words "Categories" "Clients" "Jobs" and "Notes." Many people use different words to describe the hierarchy of their data - even when that hierarchy is the same. We have to be careful implementing this, because this is a feature that could potentially enable users to "hang themselves" if they choose bad words as replacements. Being able to replace these words also makes technical support a little more difficult because we won't be able to provide instructions such as, "Select 'Clients' from the Configuration menu."
34. The ability to export time data in iCal (ics) format that can be read from iCal, Lightning or other ics capable calendars.
35. Provide feedback regarding network transfer success or failure, and potentially transfer progress.
36. The ability to provide feedback and make technical support requests directly from the device. We want to do this so that people can give us suggestions and ask for help without needing to leave the application to come to our web site.(added in version 1.3.2)
37. Location awareness. Using the built-in hardware to determine the current location and tie that into a client, job or category.
38. Integrate to the greatest extent possible with the phone, contacts list, SMS and email capabilities of the device.
39. Enable landscape mode.
40. Correct the sort order of modified entries. (fixed in version 1.3.0)
41. Configuration option for font and font size.
42. Add 6 minute interval selection for lawyers and others who bill by 1/10th hours. Included in version 1.2.3
43. Enable different views of current entries, and a configuration for the default view to display:
    • List view for month (the current view, which would be the default) (added in version 1.3.0)
    • List view for week (added in version 1.3.0)
    • List view for day (added in version 1.3.0)
    • Table view of month (due to screen size constraints, this would not contain data, but would enable the user to select a day, which would lead to a day list view of entries)
44. Add the number of started counters on the home screen. (added in version 1.3.0)
45. Ability to change the subject on the outgoing email CSV report(added in version 1.3.2)
46. When backups are saved, use the date (YYYYMMDD) or something similar in the file name to prevent overwriting previous backups. This will also need to include a utility allowing users to choose the backup from which they desire to recover.
47. Create "Add" buttons in the top right corner of administration screens for Categories, Clients and/or Jobs to eliminate the need to scroll down to add new entries
48. Email functions handled within TimeLogger rather than exiting to the Mail application.(added in version 1.3.2 -- this has only been an option since OS version 3.0)
49. Send CSV files from within the app rather than relying on a third party mail relay.(added in version 1.3.2 -- this has only been an option since OS version 3.0)
50. Be able to set an audible tone to sound at given intervals as a reminder that a timer is running. This feature will have limited utility until Apple allows developers to run programs in the background. If/when they allow that, we will consider this feature.
51. Add bi-weekly as a default view option (in addition to day, week and month). Different people will define bi-weekly in different ways, so we will put some thought into how to best accomplish this prior to rolling anything out.
52. Consider adding a calendar month view.
53. Arbitrary ordering of Categories, Clients or Jobs (instead of always being alphabetical)
54. Show more properties of started timers on the "Stop Timers" screen
55. A configuration option to turn on and off the application's deleting of associated entries when clients, categories and jobs are removed
56. Compact the Current Entries screen a little to include two lines of text from the Notes.
57. Change the behavior/enforcing of allowing people to set an end time before a start time. Due to the way Apple determines the order of date pickers, some people have a difficult time scrolling them back in the proper order to prevent them from resetting. We will change the behavior of TimeLogger so that it will allow a user to set a stop time before a start time and then warn and block the attempt only when the timer is submitted.
58. QuickBooks export
59. Export to and/or import from Google calendar
60. Total of hours on the Current Entries screen
61. On weeks that span a year (includes December 31st and January 1st), the next year is displayed in the column headers and report output for dates in December.
62. Allow customization of the email subject line for report email messages
63. Search time entries
64. A summary page with clients, hours worked for a given time interval
65. Adjust for time zone switched between start and finish
66. Consider not adjusting the end date when a start date is chosen for reports
67. Consideration of an "All Dates" button on the report details selection
68. Consider an option to default the start date of new timers to the last date of an entry
69. Option to default the stop time of a timer to 11:59 PM of the start date when the current date is past the end date
70. Configuration options to change the output date format
71. Automatically strip "@mac.com" and "@me.com" out of usernames for MobileME users

Wow! TimeLogger has already covered the needs of the majority of users, and based on the feedback we have received, people are very pleased with the time they are saving and the capabilities they have.

We obviously can't make TimeLogger do everything for everybody (and, as one of our users pointed out, EVERYBODY has their own idea of how it must work, and that way differs from EVERYBODY else's), but we feel that we're heading towards the one tool that does it for all.

Remember that if you purchase now, upgrades are always free. :-)

We sincerely hope that the current version of TimeLogger suits your needs well, and we look forward to being able to make it the perfect tool for you - if it isn't already!