Skip to content

WingRep · How it’s built

Owning the path from API to App Store.

A startup’s mobile product, with release ownership and the backend work needed to support it. My scope crossed the app, GraphQL API, and deployment pipeline.

← All work
Role & scope
Software engineer · Team product
Built with
React Native · Expo · GraphQL · AWS · PostgreSQL
WingRep’s iOS sign-in screen
WingRep’s iOS app. My role covered the mobile client, APIs, and release pipeline.

The responsibility

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, so the mobile experience depended on decisions beyond the screen itself.

Across the boundary

I built with Expo and React Native on top of the company’s existing AWS backend, and added GraphQL resolvers and a calendar integration on the server side.

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.

Shipping and feedback

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.

What I take from this

For me, product engineering includes the last mile: the permissions behind a screen, the integration it relies on, and the build that actually reaches someone’s phone. Owning those seams changes what I consider finished.