LATER

Inspiration

I built LATER because I was tired of saving links, articles, and ideas that I never actually used. My bookmarks, YouTube Watch Later, and saved posts had become a digital graveyard—full of good intentions but zero follow-through. I kept asking myself: "What did I save this for?"

The insight: People don't save links because they want to hoard information. They save because they expect their future self to need it. LATER makes that promise reliable.

What it does

LATER is an intent-based memory app. Instead of just saving a link, you capture:

• Why it matters (the reason you saved it)
• When it should return (triggered by projects, dates, or contexts)
• What to do next (one realistic, finishable action)

When the chosen moment arrives, LATER brings back the saved intention with full context and turns it into a calm, finishable session. Every completed session becomes proof that a saved idea moved your project forward.

How I built it

LATER is a native Android app built with:

• Kotlin for the entire codebase
• Jetpack Compose for modern, declarative UI
• Room (SQLite) for local-first data persistence
• Kotlin Flow for reactive state management
• RevenueCat for seamless subscription handling

The app is fully local-first: memories, triggers, focus sessions, and progress all persist on-device without requiring a backend.

Challenges I faced

1. Designing the capture flow: The biggest challenge was making the "Save the Why" flow feel effortless while capturing enough context to be useful later. I went through multiple iterations to balance depth with speed.

2. Trigger system: Building a flexible trigger system that could handle project-based, date-based, and context-based returns required careful data modeling in Room.

3. RevenueCat integration: Getting the subscription flow to work smoothly with the Test Store took some debugging, but once it clicked, it was incredibly powerful.

4. Time management: Building a polished, working app with video demo in hackathon timeline was intense. Prioritizing the core flow (save → retrieve → act → prove) was essential.

What I learned

• Jetpack Compose makes building modern Android UIs incredibly fast once you understand the declarative mindset
• Local-first apps can feel snappy and reliable without backend complexity
• RevenueCat abstracts away the hardest parts of monetization
• The best productivity apps don't just organize—they enable action

What's next for LATER

• Sync across devices (optional cloud backup)
• Natural language triggers ("remind me when I'm at the gym")
• Shared Later Moments for team projects
• iOS version

Built With

• android
• compose
• flow
• jetpack
• kotlin
• mobile
• productivity
• revenuecat
• room
• sqlite