So this is the whole thing.
Your next class, the room, and a countdown — drawn by iOS as a Live Activity, sitting where your notifications would be.
It starts on its own. It disappears when the class ends. You never open anything.
About
Not because we didn't know our timetable. We knew it. It's the same every week for four months.
We'd be deep in an assignment, completely focused, look up at the clock — and already be seven minutes late. Again.
Our calendars had the whole schedule in them. They just needed us to remember to check them, and remembering was the exact thing we were bad at.
Where it went
Flighty keeps your flight status on the Lock Screen. You glance at your phone and you know your gate and your boarding time. You don't open it. You don't remember to check it. It's just there when you look.
Why didn't something like that exist for classes?
The more we looked at it, the more the calendar felt like the wrong shape. A calendar assumes every week is different and that other people send you invites. A timetable is the opposite. It barely changes for a whole semester, you already roughly know it, and the only part you ever actually need is the next one, right now.
So we built for that instead. It's our first iOS app — SwiftUI, and a lot of late nights.
There are no investors here, and no advertising business. Worth saying plainly, because it's why the privacy stance is easy to hold: there's no version of this where your timetable is worth more to us than it is to you.
Your next class, the room, and a countdown — drawn by iOS as a Live Activity, sitting where your notifications would be.
It starts on its own. It disappears when the class ends. You never open anything.
The first release does one thing: your next class, visible without unlocking. The changelog tracks what's actually shipped, and nothing gets described there before it exists.
Questions, feedback, or a bug — hello@timetide.eu. We read everything.