Skip to content
Sabin Poudel

Index

Case study · Books & Reference

Scrivenn

A reading and writing community: write books, poems and blogs, join book clubs and enter writing competitions.

Role
Full Stack Mobile Developer
Company
CSP Ventures LTD
Platforms
Android · iOS
Downloads
1K+

Team project; the repositories predate my involvement. The work listed here is the part I built.

Built during my role as Full Stack Mobile Developer at CSP Ventures LTD (Apr 2025 – Oct 2025).

Scrivenn store graphic, “Discover your next great read”, showing top writers and a Continue reading card

Context

Scrivenn is a home for people who write and people who read — books written chapter by chapter, poems, blogs and private journals, with book clubs and writing competitions around them. It is a Flutter app for Android and iOS on top of a Node.js, Express and MongoDB API.

What I built

Accounts & sessions

  • Google sign-in on the Express API, issuing JWT-based sessions.
  • Refresh-token rotation and server-side revocation.
  • App authentication rebuilt as a BLoC on Clean Architecture.
  • Refresh-and-replay on 401 across all three of the app’s HTTP clients.

Real-time & notifications

  • The Thoughts feed, with live updates over WebSockets.
  • Notifications, and per-device push through Firebase Cloud Messaging backed by a device and app-version registry.

Reading & discovery

  • Reading lists, reading history and genre-based recommendations.
  • Tag suggestions backed by Typesense.
  • Onboarding with genre selection.

Writing & community

  • Book clubs and writing competitions.
  • A co-author picker for shared works.
  • Editor autosave, word count and focus mode; annotations.

Sharing & links

  • QR-code profile sharing and scanning.
  • Android App Links for profile, reading and invite URLs.
  • Sharing a work as a link or as an image.

Operations

  • Request and application logging with Winston and Morgan.

Engineering notes

  1. One session, three HTTP clients

    The app reaches the API through three different HTTP stacks. Token refresh is centralised, so whichever client gets a 401 refreshes once and replays the original request. On the server, refresh tokens rotate on use and can be revoked.

  2. Push that knows the device

    Push notifications are addressed per device through a registry keyed to each installation and its app version, so a person with two phones gets the right notifications on each, and older builds can be handled deliberately.

  3. Links that land on the right screen

    Profile, reading and invite URLs open directly in the app through Android App Links, with a guard so a single link never pushes the same screen twice.

Stack

  • Flutter
  • Dart
  • BLoC
  • Provider
  • get_it
  • dio
  • Node.js
  • Express.js
  • MongoDB
  • Socket.IO
  • Firebase Cloud Messaging
  • Typesense