Took an existing web marketplace app connecting homeowners with contractors to native mobile and published it to both app stores, working solo from a Windows machine with no Mac hardware anywhere in the pipeline.
Build and release pipeline
The compliance pass is drawn as a gate because it is what actually decides whether a build ships. Most rejections happen there, not in the code.Shipped build: the contractor home screen, a live session with photo exchange, and the ported AI feature turning a finished job into a written, SEO-tagged page.
Engineering highlights
Ported an AI content-generation feature from a sister product, where a voice note and job photos become a written write-up, social posts and a review request, and fixed real defects in its outbound integration contract along the way
Diagnosed platform-specific failure modes invisible from the web codebase: a browser API call that works fine in a browser can silently terminate the native iOS process unless the native permission manifest is updated in parallel
Built and owned the entire signed release pipeline, build signing, versioning, store metadata and review submission, with no local Apple hardware
Result
Approved by Apple on the first submission, in a case where an earlier app from the same publisher had been rejected three times. Live on both stores, with the first real business customer onboarded to the AI content feature and verified end to end after launch.