A screen can look finished while its data and backend behavior are still unreliable. Stale state, incomplete API responses, missed notifications, and interrupted checkout often cross repository boundaries. I work across the mobile client and backend integration to make the complete user journey understandable and testable.
I connect authentication, request and response models, pagination, uploads, and error handling. The app needs a defined response to slow connections, expired sessions, partial data, and retries. I can adapt an existing REST API or implement the backend changes the mobile flow requires.
Cloud and operational workflows
My delivered work includes Firebase authentication, Firestore, Cloud Functions, notifications, and analytics, alongside PHP and Django backends. I can also assess Supabase integration for a product’s needs. Service selection starts with the current data, access rules, and operational constraints.
Consistency across system boundaries
I investigate flows that continue when the app is closed: payment callbacks, background jobs, notification delivery, and scheduled state changes. That includes deciding which system owns the state and how the client recovers when a response is delayed or a request is repeated.
Follow one user journey through the system
Bring the app, API documentation if available, and the flow that needs to work. I trace it from the interface through the server and back, agree on data and failure behavior, then verify the integration in the appropriate test environment before release work begins.
Built discovery and booking-request flows with a Django REST backend and asynchronous jobs. The product is now discontinued; the case study documents the delivered work.