Reading app — delivered on the launch date.

Solution
Build
Effort
2 FTEon average
Duration
1 year2024–2025
Status
Completed

01 · The client

A major publishing group that wanted to try a reading format new to its market: serialised fiction designed for the phone, delivered through its own app rather than through bookshops.

Type
Publisher
Region
Italy
People
Over 1,000
Stage
New product line

02 · The trigger

The launch date was set before a single line of code existed.

The marketing campaigns were already planned. They needed an app ready for readers, on iOS and Android, with no room to rebuild it later.

03 · The technical problem

Fixed deadlines, finished-product quality, costs under control: you usually get two out of three. On top of that, a reading app has to stay smooth across a huge range of phones, and the backend has to handle traffic that doesn't arrive evenly but in waves, when campaigns go out.

04 · What we did

A single Flutter codebase for iOS and Android: one place to build, one place to fix. Short cycles with the client's team, so every feature was seen and validated right away, and priority changes — which always come during a launch — were absorbed without stopping everything. Underneath, the backend's AWS infrastructure, defined as code and deployed automatically: services that grow with the load and shrink when it drops, monitoring and alerts, fast releases and safe rollbacks.

05 · The partnership

  1. 2024

    One codebase, two stores

    The iOS and Android app built in Flutter.

  2. 2024

    Infrastructure that follows the load

    The backend grows with campaigns and shrinks after.

  3. 2024

    Launched on time

    Release aligned with the planned campaigns.

  4. 2025

    Partnership completed

06 · Where things stand now

The app shipped on time and passed ten thousand downloads, with an average rating of 4.6 stars.

Lane: Build ·  Vertical: Publishing & Media

Write to us