I built Jiffy for people who don't want to maintain a system. Write down what matters, when it matters, and trust the app to handle the structure. The whole product direction was about reducing setup, reducing taps, and reducing decision fatigue.
Every reminders app I tried eventually became something I avoided. Too much setup, too many taps, too much cognitive overhead for something that should take two seconds. Jiffy started as a personal frustration — I just wanted to write things down and trust the app to handle the structure.
Instead of forms and pickers, Jiffy lets you write 'Doctor appt on the 22nd at 11.30am' and figures out the rest. The goal was zero ceremony — open, type, done. I spent a lot of time on the parsing because the interaction model depends on it feeling instant.
I took cues from conversational products I actually enjoy using: clear hierarchy, generous spacing, obvious next actions. The UI should disappear. Your notes, tasks and reminders should be what you see.
I built shared spaces for families, couples, friends — places where notes and reminders live together without the chaos of a message thread. Coordinating with people shouldn't mean switching between three apps.
Shipping is easier than ever. The harder problem is knowing what should exist at all. I cut more features from Jiffy than I shipped. Fewer noisy things, tighter defaults, stronger clarity. That constraint became the product's point of view.
I didn't try to reinvent every interaction. Instead I improved familiar patterns with more precision and less friction. That made onboarding easier for people coming from existing tools, while still giving Jiffy a distinct feel.
Capture, scheduling, and sharing. By keeping the interface familiar and the interaction model conversational, I tried to build something calmer — for people who want help staying on top of life without becoming power users first.