0

I'm building an application where a user should be able to enter a date, but where I want to allow for "approximate" dates, such at the 19th century or the 1950th. Sometimes the user also knows the month and date, sometimes not.

I could do this with various options and selectors, but since this will be used over and over again, I would really like it to be quick an easy.

From a logical views, it should be fairly straight forward since you start by entering the century, then (optionally) a decade, then (optionally) a year etc. But I can't get my head around how you would design this in an intuitive matter where a user can enter this quickly.

2
  • What is the purpose of your application? What type of information will be presented back to your users? Will most users be entering a date only once? Or will they be using this selector multiple times in a row? Will this be an entertaining app to interact with or purely informational/productivity based?
    – It's Dylan
    Commented Apr 18 at 21:08
  • 1
    An idea is having a single input field for the date and when something is typed in fitting suggestions will pop-up to select from. This obviously needs some more development and testing time to be able to give reasonable suggestions.
    – jazZRo
    Commented Apr 19 at 9:05

2 Answers 2

1

Genealogy apps (like MyHeritage, for example) have the similar problems that they solve somewhat ok, i think.

What they do is adding a dropdown before the date picker to choose what kind of date it is: exact, circa, unsure, before, after, etc.

A birth date input featuring a precision dropdown in addition to traditional date input

This particular dropdown has these options, that make sense in genealogy world (because sometimes you get data from testimonies, or partially readable gravestones, or whatever), but you can see whichever you need.

Different options of the precision dropdown

Interestingly enough, they allow even more complex structures: like if you know the date period, they allow you to enter more than one date:

A "between" precision input, that allow two dates to be input as a period

Hopefully it helps.

0

Based on what you have described, there really isn't any standard input field that will satisfy the various inputs that the user can provide, except for a free text field. But this means you will have to do a lot of work to ensure that the data can be understood and processed unambiguously.

Rather than potentially creating a lot of work for yourself, it might be easier for the user to enter a standard date containing the year, month and date, and then give them an option to see the range of dates that should be searched for. This is similar to a user selecting a location on a map and then specifying the radius around the area to search for.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.