Owning the path from API to App Store.

At WingRep.ai, I led the iOS app from its build pipeline to App Store launch. I worked on a team product, owning the mobile implementation and releases alongside backend infrastructure.

The product supported goals, meetings, and scheduling. Reps and managers needed different views and permissions over shared data, so the mobile experience depended on decisions beyond the screen itself.

I built with Expo and React Native and architected a serverless AWS stack using CDK, AppSync, Lambda, and Aurora PostgreSQL. The work included Python GraphQL resolvers, Google Calendar integration over OAuth, and GitHub Actions CI/CD.

That scope made API behavior, authorization, and mobile state part of one engineering problem. A screen could look complete while its integration or release path still needed work.

I owned cross-device UI work and the release process through App Store launch. I also recruited pilot users and gathered feedback through Slack.

One product iteration removed an emotion picker after a simpler survey worked better in testing. The useful engineering decision was to simplify the flow instead of continuing to invest in a more elaborate interaction. This was qualitative feedback, not a measured conversion result.