Movies Calculator

Movies Calculator started from a personal itch: I wanted to know how much of my life a franchise marathon or a director’s full filmography would actually cost me, and every existing tool either didn’t exist or buried the answer in a spreadsheet. The brief I set for myself was to make the single number — “how many movies can you watch” — instantly answerable, then give people a reason to keep exploring once they had it.

The constraint was that this had to be a one-person build: no design team, no dev team, no content team. Every decision needed to earn its place against my own time budget, and the product needed to be able to grow (new franchises, directors, guides) without me manually designing every new page.

How I framed the problem

The real challenge became three connected products: an instant calculator, a scalable cinematic content library, and a personal planning layer that gives people a reason to return. The system needed to move naturally from a one-off calculation into a persistent watchlist, customizable identity, social sharing, achievements, and an optional paid upgrade — without making the free experience feel incomplete.

Principles for this project

• One answer, above the fold: the calculator inputs and result had to resolve without scrolling — everything else is optional depth.

• Dark, cinema-adjacent surface: a near-black UI with a single green accent nods to a theatre/streaming context without leaning on movie clichés.

• Systemized content, not one-off pages: franchises, directors, actors, and runtime tables all share one component language so the library can grow without new design work.

• SEO architecture as product design: URL structure, internal linking, and page templates were specified at the same time as the visual system — not bolted on afterwards — so search visibility is structural, not incidental.

I audited existing runtime and “how many hours” tools and found most were either static blog listicles or spreadsheet-style calculators with no visual identity and no path to related content. None combined a live calculator with an explorable database.

• Search demand clustered around specific, answerable questions — “how long is the MCU”, “Harry Potter watch time” — not generic calculators.

• Franchise and filmography runtime data was scattered and often wrong; a manually curated dataset would be a real differentiator, not just content filler.

• Visitors compare more than they calculate — franchise vs. franchise, streaming platform vs. streaming platform — so comparison pages needed to exist from day one, not as a later feature.

I evaluated several data sources before settling on TMDB for movie metadata and JustWatch for streaming availability. TMDB offered a well-documented public API with broad coverage of films, directors, actors, and posters, and a permissive attribution-based licence that suited a self-funded project. JustWatch provided the most complete and up-to-date platform availability data across regions — far more accurate than scraping or manual upkeep. Using both APIs in combination gave the site a content pipeline that could grow without manual data entry for every new page.

I tried three directions for the core interaction: a single free-text input (“ask anything”), a slider-based estimator, and a structured four-field form (daily hours, speed, horizon, movie length). The structured form won — it removed all ambiguity about what the number meant and made results shareable and comparable.

For the visual system, a bright, poster-collage aesthetic was tempting given the subject matter, but it fought with the data-dense franchise and runtime pages. Settling on a restrained dark UI with a single accent colour let movie posters and imagery do the visual work instead of the interface competing with them.

The calculator sits at the centre of a much larger structure: curated franchise pages with poster grids and hour totals, director and actor filmographies, a full runtime reference table, head-to-head comparison pages (MCU vs. DCEU, Star Wars vs. Lord of the Rings), and a guides section covering watch habits, marathons, and streaming platforms. A shared footer and mega-menu tie every section together so a single search intent can lead into related content instead of a dead end.

Every layer — logo, calculator card, franchise card, FAQ accordion, and footer sitemap — was designed and built by me alone, from first sketch to shipped product, then launched publicly on Product Hunt.

The account layer turns the calculator from a single-use utility into a personal movie companion. Each user can claim a customizable handle, choose a profile color, build a private viewing queue, mark films as watched, and share a public watchlist profile with friends. The shared profile makes recommendations and marathon plans portable: instead of sending screenshots or a list in chat, users can share one continuously updated destination.

I added a lightweight achievement system to make progress visible without turning movie watching into a competitive leaderboard. Users collect badges for viewing milestones, completed marathons, and queue goals. A paid Pro plan extends that system with advanced achievements, richer queue planning, and streaming-availability tools, creating a clear upgrade path while keeping the calculator, account, profile, and core watchlist useful for free.

The content architecture was built around a deliberate SEO structure from the ground up. Each section of the site — franchises, directors, actors, runtime tables, comparisons, and guides — targets a distinct cluster of search demand, with URL patterns, heading hierarchies, and internal linking designed to make the full library discoverable. Programmatic pages (franchise, director, and actor filmographies) share one reusable template with correct canonical URLs, structured data, and social metadata so the library scales without duplicate-content or indexing problems. The result is a site where well-known queries like “how long is the MCU” or “Christopher Nolan filmography runtime” resolve to a precise, first-party-curated answer instead of a Reddit thread.

The data layer runs on a pipeline built around the TMDB and JustWatch APIs. TMDB supplies movie metadata — titles, runtimes, posters, cast, and crew — which populates director filmographies, actor pages, and franchise detail pages automatically. JustWatch provides streaming availability data, feeding the “where to watch” guide content with current platform and region information. Franchise groupings and watch-order sequences sit outside this pipeline as manually maintained datasets, keeping the curated quality of the most-visited pages high without committing to fully automated data for content where accuracy matters most.