🚀 Join the crew - Applications now open

Factor16/Case study

A complete ticket scanning inbox in 30 minutes

Pokerbase needed a full ticket scanning inbox for their React Native app. Backend API, frontend screens, tests, security review, and a deploy-ready build. A senior developer estimated 8 hours. We delivered it in 30 minutes, and caught a feature gap the original spec missed.

Total delivery
30 min
Human time
5 min
Faster
16×
The challenge

Build a ticket scanning inbox from scratch

Pokerbase is a poker session management app built with React Native. Their users needed a way to scan physical tickets, store them in an inbox, and link them to poker sessions, either during session creation or retroactively.

The feature crossed the whole stack: a new database schema, REST API endpoints, React Native screens with camera integration for scanning, navigation updates, and proper test coverage. Security mattered; the tickets contain financial data.

A senior developer estimated 8 hours. That's a full work day blocked on a single feature.

What we delivered

  • Backend API & database schema
  • React Native screens & navigation
  • QR code scanning integration
  • Automated test suite
  • Security review & auth checks
  • Feature enhancement caught during review
Pokerbase ticket scanning inbox on iOS, showing a list of scanned tickets linked to poker sessions
Execution timeline

From requirement to production, in 30 minutes

How the 30 minutes broke down, from first requirement analysis to a deploy-ready build.

  1. 1
    0–10 min
    Requirement refinement & architecture

    We analyzed the ticket scanning inbox requirement. During analysis we spotted a gap: the original spec only covered creating new sessions from inbox tickets, not linking tickets to existing sessions. We designed the data model and user flow before writing any code.

  2. 2
    10–25 min
    Full implementation

    Backend API endpoints and database schema. React Native screens: inbox list, ticket detail, and the linking flow. Test cases written in parallel using TDD. Auth concerns on the new endpoints flagged and resolved. Build pipeline configured.

  3. 3
    25–30 min
    Human review & iteration

    The reviewer tested the feature in the app, flagged a color scheme inconsistency, and approved the feature enhancement spotted during analysis. Ready to ship.

Let's talk about your project!

Connect with us, and let's discover how we can turn your vision into a seamless, impactful solution.