FuelBuddy's customer app started as a Progressive Web App. That worked on Android, but on iPhone it hit a wall: Apple only allows web apps to run on its own WebKit engine and gives them second-class treatment — unreliable install-to-home-screen, limited storage, and no dependable push notifications — to the point of moving to strip Home Screen web apps out of iOS entirely. For FuelBuddy that meant the PWA effectively couldn't serve iPhone users, and a native app was the only reliable way to reach them. I was part of the engineering team that rewrote the app in React Native.

What I worked on

PWA to React Native: Rewrote the app as a compiled React Native application, focusing on the mobile UI and making sure it felt native on both iOS and Android rather than like a wrapped web page.
Working across the stack: My main focus was the mobile frontend, but when a feature needed new data endpoints I built the CRUD APIs myself on Hasura's GraphQL engine, so the work didn't stall waiting on another team.
Shipping with the team: Worked closely with the other developers and product owners to turn requirements into finished features and keep releases moving.

Why it mattered

Going native got FuelBuddy off the platform it couldn't rely on and put a single, consistent app in front of customers on both iPhone and Android. Pitching in across the stack helped the team keep up the pace of releases.