Exam Countdown App — Know Exactly How Long You Have

Every countdown in the app answers the same question — how long do I have? — but not every deadline looks the same. A final exam has a fixed date. A class test needs its own reminder. A board hasn't announced the date yet. An admission test isn't tied to any subject at all. The countdown system is built to handle all four honestly, rather than forcing everything into one date field.

There are two kinds of countdown in the app:

• Subject-linked exams — attached to a subject in your syllabus, set from that subject's page. This is where a subject's final exam date, its class tests, and its tentative/TBA handling all live.
• General countdowns — a standalone date with just a name, a colour and a time, not tied to any subject. Admission tests, viva dates, a scholarship deadline, a project submission — anything you want a countdown for that isn't part of a subject's syllabus.

Both feed the same home screen, and both can become the big hero countdown at the top of the app.

Open a subject and tap its exam date, and you choose one of three ways to describe it — because "when is the exam" doesn't always have a clean answer:

• Exact Date. You know the date and time. Pick it, and the app shows exactly how it sits relative to today — Today, Tomorrow, In 12 days, or 3 days ago if it's slipped into the past. The card's status colour tightens as it gets close: green with room to spare, orange under a week, red under three days.
• Tentative. You don't have a date, but you know roughly which month — "sometime in March." You pick the month from a row of chips, and the app does the sensible thing with it: if that month has already passed this year, it counts toward next year's occurrence, so a tentative "March" set in October means next March, not a March you already missed. On the home screen this shows as This Month, 1 Month, or N Months rather than a day count you have no real basis for.
• To Be Announced (TBA). The exam date genuinely isn't out yet. Rather than showing nothing, the app is upfront about it — "The exam date hasn't been declared yet" — and offers something more useful than waiting: a Target Preparation Date.

This is the answer to a real problem: how do you stay motivated to prepare for an exam whose date doesn't exist yet? You set your own deadline — "I want to be ready by the 15th" — and the app runs a genuine live countdown against it, exactly like it would for a real exam date: days remaining, the same colour thresholds, the same urgency as the exam gets closer.

If that self-set date passes before the real exam is announced, the card doesn't pretend nothing happened — it switches to Overdue, in red, so you know your prep target came and went before the actual news did. You can edit or clear the target date at any time from the same TBA card, without needing to know the real exam date to do it.

A subject's exam page has a second section below the main exam: Class Tests & Short Exams. This is a running timeline of every smaller assessment for that subject — unit tests, quizzes, presentations, viva dates — each with its own title and date/time, added inline with a simple form and shown as a vertical timeline sorted chronologically. Each entry can be edited or deleted, and every one gets its own relative-time label the same way the main exam does.

This matters because the "next thing due" for a subject is often not the final exam. A class test next Tuesday is more urgent than a final exam in four months, and the app treats it that way: everywhere a subject shows a countdown — its card on the home screen, the number in its ring — it's actually showing the nearest upcoming date across the main exam and every class test combined, not just the final exam. Once that class test passes, the countdown automatically moves on to whatever's next in the timeline, main exam included.

For a date that has nothing to do with a subject's syllabus, there's a simpler dialog: a name, a date and time, and a colour. That's it — no tentative or TBA modes, because a general countdown is something you already know the date for by definition. These live in their own grid alongside the subject-linked exams, sorted with past ones pushed to the end and everything else by how soon it's coming.

The big countdown at the top of the app — the one ticking down live, second by second — isn't a separate thing you configure. It's resolved automatically from everything you've already entered:

• By default, it shows the single nearest upcoming date across everything: every subject's main exam, every class test, and every general countdown, all compared at once. Whatever is genuinely soonest wins, and it updates itself automatically the moment something more urgent appears or the current one passes.
• You can pin any specific countdown instead — a subject's main exam, one particular class test, or a general countdown — and the hero locks onto that one regardless of what else is nearer, until you unpin it.
• It ticks every second, and the same live number is pushed out to your home-screen widgets, so the countdown on your phone's home screen and the one inside the app always agree.

Every countdown, subject-linked or general, is really just: pick the nearest qualifying date, subtract today, show what's left. What differs is which dates qualify and how the gap is displayed:

• The Diya dashboard's readiness forecast takes your exam date and your measured syllabus pace and projects whether you'll actually be ready by then — this is the card that turns a countdown from "how long is left" into "is that long enough." A subject on TBA or tentative without a resolvable date simply doesn't get a forecast, since there's no real deadline yet to project against.
• The Study Planner reads a subject's exam date directly when working out where your revision phase should end. A confirmed exact date gives it something solid to plan against; a subject still on TBA is one the planner can't yet build a revision phase around.
• Multi-device sync keeps every countdown consistent by timestamp — editing a countdown's name or date on one device and a different one on another never makes you pick a winner; whichever edit actually happened later is the one that survives the merge, and a deleted countdown carries a record of its own deletion so it can't quietly reappear from an older sync.

The whole system is built around one idea: a countdown is only useful if it's honest about what it's counting toward. A vague "sometime in March," an unannounced date you're preparing for anyway, and a definite exam next Tuesday are three different kinds of certainty — and the app shows you the difference instead of flattening them into the same number.