Let's talk
← All work

(Case study 06 / 07 — Mobile · React Native)

React Native App

13

Home sections the product team edits live

Role
Built the homepage, debit card controls and push notifications in the rebuild from Flutter to React Native.
Status
Released.
Stack
  • Expo
  • TanStack Query
  • Reanimated
  • Zustand

(01) The problem

The consumer app was being rebuilt in React Native, and the product team wanted to change the homepage without shipping an app release.

(02) What I built

  • A server-driven homepage: CMS layouts decide which of 13 sections render, and in what order.
  • Bundled offline copies of every layout, and a CI test that fails on any broken deeplink. It found 26, now fixed.
  • Debit card lock, block, channel toggles and limits, each verified with OTP, with a 3-attempt lockout.
  • Push notifications through FCM and APNs, routed through the app's deeplink registry.

(03) The hard part

A bad CMS document can break a server-driven screen. Every content read goes through one fetch function with a bundled fallback, and the mappers fail safe, so an unreadable response never downgrades an active user to the first-time view.

(04) Result

Live in the released app: homepage content and section order change from the CMS without an app release.

Next case studyRedCell

(Hiring? Let's talk)

Let's buildsomething that ships.

Say hello