When creating a new entity in an iPad application one of the mandatory properties is a deliver date. There is no way to predict this deliver date. Choosing the wrong deliver date leads to all kinds of problem. My idea is that by forcing the user to select a date, rather than providing a default one, some thought will go into selecting the date and thus minimize faulty dates.
Normally when a new entity the user has some kind of paper as a base. Later on changes are made to the entity but the paper used when creating the entity is not necessarily available. Which means that the deliver date should be selected when creating the entity. It is possible to change the deliver date after the entity is created.
The problem with the standard date picker control on iOS is that it is not possible to start in an unselected state. How can I force the user to make an active choice when selecting the deliver date? After the entity is created the normal date picker would work fine but I would prefer to use the same method for selecting the date in both cases.
There is an interval of valid dates but the interval is quite big which means it is not really practical to start an invalid date and force the user to scroll to a valid date.