Up until now I’ve been using separate views for Event Detail (view only) and Event Edit. I decided to try to combine these into one view and work them into the main navigation stack. This way event data entry can be done without opening a modal. Adding a new event will still be done in a modal though.
I have two versions of this.
Option 1 is pretty much the old event edit view with some “time passed” calculations in the section footers below the dates.
Option 2 is a version where I renamed the segmented control for End Date and changed the labels. Instead of asking the user to select what type of end date they want (none, closed, ongoing) I ask them what type of event they want (single date, date range, ongoing event). I think this helps clear up some confusion as it’s much easier to explain what an event type is then it was trying to explain the nuances of end dates.
Dave and I discussed these options on Project Update episode 17 yesterday and he gave me some ideas. We both agreed that option two was the better choice out of the options above. Dave had a couple of suggestions.
- Change the Ongoing icon back to the empty circle to differentiate them from end dates.
- Change the Event Type control to omit the Ongoing option. Users can select either Single Date or Date Range
- If the user selects Date Range as the Event Type then show an additional control in the End Date section where they can mark an end date as Ongoing.
This is my first pass at implementing these suggestions. I added a toggle to the End Date section. If this is false (default) then the date picker will show. Otherwise the date picker will hide and the Ongoing symbol is shown with the label.
Side note: the End Date section footer in this image has not been updated to omit the time passed string when an end date is set to Ongoing.
I’m not sure if I like this change or not. It might be a little easier to understand, which is the most important factor for this screen.