Poster-first search
Recognize a film at a glance, choose it quickly, then move straight into logging or saving.
Afterframes is a private cinema diary for logging what you watch, understanding your taste, and deciding what deserves the next evening.
Keep the feeling, the rating, and the moment together.
Every part of Afterframes is shaped around a quiet loop: find something, watch it, record what mattered, and let your own history improve the next choice.
Recognize a film at a glance, choose it quickly, then move straight into logging or saving.
Rate, date, rewatch, and write only when you have something worth keeping.
Picks informed by your ratings—not a generic popularity chart—with the taste connection made clear.
Keep the films you mean to watch and bring useful viewing context into one calm view.
See patterns in genres, directors, ratings, and rewatches without turning your taste into a corporate dashboard.
Afterframes is designed around private reflection first. Sharing can be intentional; performance never has to enter the room.
Remember the film—not the feed around it.
Your diary is not a follower count, streak competition, or engagement machine.
Ratings, rewatches, notes, and changing opinions make the record richer over time.
Posters and words lead. Interface noise stays out of the way.
Join the private beta list for launch notes and an invitation when the first TestFlight group opens.
One email when the private beta opens. No spam, unsubscribe anytime.
These concise policy outlines are a working foundation, not final legal documents. They should be completed with the app’s actual data practices and reviewed by qualified counsel before launch.
What the final policy should cover:
Private diary entries should be described accurately based on the shipped architecture; “private” should never imply encryption or access controls the product does not provide.
What the final terms should cover:
The final language should match the launch region, business entity, billing model, and actual product behavior.
A public support channel is required before App Store submission. Add the verified support email or help-desk URL here once it is chosen; do not publish a guessed address.
Recommended launch coverage: sign-in help, account deletion, data export, content corrections, accessibility issues, subscription questions, and a response-time expectation.