... instead of piling on features, i spent the whole build obsessing over those 3 seconds, type it the way you'd say it .. "dentist thurs 2pm", "gym mon wed fri 6am" .. and it figures out the date, time, and recurrence, then shows you what it understood before you commit .. no form, back to work in seconds PopTask v2.3 went live today but honestly i'm more curious about the debate: what's in your to-do app graveyard?  name ... ... doesn't just become another graveyard? Comment from Gal Dayan(@galdayan): my graveyard entry is Things 3, not because it lacked features but because opening it felt like starting a mini project just to write "buy milk". the capture-vs

... nobody admits to your question is the right one though .. a wrong-time task really is worse than no task, so it never commits silently: before you hit add, it shows you what it understood (title, date, time, recurrence) right there in a preview .. a wrong 6am reads back as "6:00 AM" and you fix it in one tap before it's ever a task .. the rule is basically, never make someone trust a guess they didn ...

... real testing is required. 5. If you need reliable behaviour across Google, Outlook and Apple You can manually maintain: Vendor specific logic Timezone normalisation rules Multiple schemas for ICS, Google API and Microsoft Graph Workarounds for SEQUENCE and RECURRENCE edge cases Testing infrastructure for every update scenario Many teams try this and eventually realise it becomes its own infrastructure project. If you want to avoid building that system yourself, Synara handles the cross vendor differences automatically: https://synara.events Synara validates ...