ROOTATOM / PRODUCT NOTES

Recent ROOTATOM releases, without pretending we are at v1.

A record of the product and deployment updates that shape the practice experience.

Logged releases and milestones
15
Current release
v0.9.3
Product stage
Pre-v1

Paper 4 upgrade · v0.9.3

Paper 4 grouped theory layout

Added a cleaner Paper 4 practice flow for Chemistry and Physics so theory questions stay grouped with their stems, context, and matching subparts.

  • Grouped Paper 4 subparts into one practice card per theory question instead of splitting related context apart.
  • Added Chemistry and Physics subject shortcuts on the Paper 4 question-bank flow.
  • Improved Paper 4 question cards with stem context, dependency notes, and chapter-matched subparts.
  • Grouped Paper 4 cards
  • Chemistry and Physics support
  • Better theory context

Current release

Deploy hardening · v0.9.2

Static recovery and deploy hardening

Locked the premium UI assets back into the shipped build so the polished frontend survives production deploys.

  • Restored premium cursor, haptics, and supporting vendor bundles inside collected static assets.
  • Fixed the favicon include so branded browser tabs resolve correctly from Django static paths.
  • Added collectstatic to the Docker build to keep production bundles synced before release.
  • Production-ready static sync
  • Premium assets restored
  • Favicon path cleanup

Feature drop · v0.9.0

Premium cursor and interface polish

Introduced the premium interaction layer that makes the site feel more deliberate without pretending this is v1 yet.

  • Added a custom premium cursor treatment with dedicated arrow assets for default and active states.
  • Refined footer-level asset loading so the cursor and haptics initialize from the shared site shell.
  • Tuned the premium UI styling pass to support the new motion and pointer treatment across pages.
  • Premium cursor rollout
  • Interaction polish pass
  • Shared shell asset loading

Earlier milestones

Small steps across the product.

  1. Practice flow · March 8, 2026

    Timer surfaced higher on practice pages

    Moved the timer into a more obvious position so timed sets feel clearer under pressure.

  2. Practice flow · March 8, 2026

    Timer behavior pass

    Tightened the practice timer experience so pacing cues feel less awkward during question sessions.

  3. UI polish · March 8, 2026

    First premium cursor experience landed

    Shipped the earlier premium pointer pass that set up the later cursor and motion polish.

  4. Infrastructure · March 6, 2026

    Deploy requirements stabilized

    Added the runtime dependency needed for production serving so deploys stop failing on missing app server tooling.

  5. Practice flow · March 6, 2026

    Question answering UI simplified

    Reduced visual clutter in the answer flow so the practice interface feels lighter and easier to parse.

  6. Competitive · March 6, 2026

    Leaderboard visual upgrade

    Refreshed leaderboard presentation and related practice surfaces to feel more premium and easier to scan.

  7. UI polish · March 6, 2026

    Premium QA styling pass

    Improved the look and feel of question-and-answer screens ahead of the later simplification work.

  8. Quality · March 4, 2026

    Question report workflow introduced

    Added the reporting path that lets users flag question issues instead of silently working around them.

  9. Interaction · March 4, 2026

    Site-wide haptics rollout

    Expanded haptic feedback beyond one screen so interactions feel more tactile across the product.

  10. Homepage · March 3, 2026

    Hero and feedback system improved

    Strengthened the home page atmosphere and tied it more closely to the new interaction feedback layer.

  11. Homepage · February 26, 2026

    Hero screen styling overhaul

    Reworked the home page styling foundation to make the product feel more intentional and less generic.

  12. Homepage · February 26, 2026

    Hero screen appeal upgrade

    Started the visual push on the landing experience with stronger layout, hierarchy, and visual energy.

The UI work is still intentionally pre-v1. The goal of these releases was not to explode scope, but to tighten the visible experience, fix the missing assets that broke it in deployment, and make the Docker build ship the same interface that worked locally.

  • Small releases with explicit commit-backed notes.
  • Product changes focused on practice clarity.
  • Deployment work keeps the shipped experience close to what worked locally.