Unit & Measure Converter on two phones: the Categories screen and the Converter screen

My First iOS App

Product & Platform
Unit & Measure Converter, native iOS app
Timeline
Mar – Aug 2026
Impact
Designed, built and launched my first iOS app, now live on the App Store

AI is evolving fast, and new tools come out every day. As a product designer, I wanted to explore, learn, and see if I could build my own product. Working with Claude, I vibe designed, coded and launched my first native iOS app, Unit & Measure Converter. The whole process took 62 hours, from idea and product requirements to building, testing and App Store launch.

Scan the QR code to try the app, or view it on the App Store.

QR code to Unit & Measure Converter on the App Store

My Role

  • Product manager

    Clarified the problems, researched similar apps, wrote the PRD, and defined the scope and priorities for the initial launch (P0) and future features.

  • Project manager

    Planned the project in phases, from research and product requirements to design, build and test, and launch. Ran it step by step and documented every decision and time cost.

  • UX/UI designer

    Defined the design system and owned the UX and UI of every feature, accessibility, branding and the App Store listing.

  • Engineer

    Built the app’s logic and interface through Claude Code in 184 commits. Reviewed, tested and launched the app.

From Ideas to Product Requirements

I grew up with the metric system. I know how 26°C feels, but I’m not sure about 78°F. The popular converter apps I used weren’t quite right for me, and I had feature and design ideas for a better app that fit my own needs.

Starting with those ideas, I did competitive research, brainstormed features, and expanded them into a detailed product requirements doc. To stand out from other apps and give the product a clear identity, the app focuses on three key aspects.

Personalize
Most people use a few units all the time and rarely touch the rest, yet existing apps require scrolling through a long list every time. Favorites should be pinned and visible as soon as the app opens.
Memorize
Some numbers get converted again and again, like 78°F. The app should save value pairs, remember history, and export a set of values as text or an image, so users can copy or print them.
Simplicity
A utility app should be simple and fast: no distracting ads, no tracking, and no network needed.
The product requirements document: problem, three pillars, personas, feature scope from P0 to out of scope, core screens, build phases and open questions

Vibe Design

Start from words, then wireframes

I began by describing the wireframe structure in words: the key screens and flows. Claude turned my descriptions into low-fidelity wireframes, so I could check the structure and states, like empty favorites and edit mode, before any visual design.

Early greyscale wireframes of two screens: the categories list with favorites, and the converter with saved values and a number pad

Sketch when words fall short

Along the way, I found that in some cases a quick paper sketch got an idea across to Claude faster and more accurately than a description, like the onboarding pages.

A paper sketch of an onboarding screen, with notes for the feature name, details, a UI example and the Next button

Design system and details in Claude Design

In Claude Design, I explored several directions and chose a calm, cool-toned design system that conveys simplicity and reliability. For P0, I covered the accessibility fundamentals: contrast, small screens and basic VoiceOver. Dark theme, high contrast and other devices are future enhancements. Then I worked through each feature’s details and flows.

The app's design system in Claude Design: the colour palette and the type scale

Prototyping throughout

As I designed the details in Claude Design, the design became a clickable prototype that runs in a web browser. I tested the designs on different phone screen sizes, and also designed some of the interaction and haptic behaviors along the way. Later, the prototype became the reference for the build.

The clickable HTML prototype running in a browser, showing the Categories screen in a phone frame

Tech Development Plan, Vibe Coding & Testing

Learn the process before building

Instead of asking Claude to build features right away, I first asked it to teach me and recommend the right development process. Then, with my PRD, I asked Claude to create a detailed project plan: high-level phases, and small steps that each focused on a single topic.

The plan had 14 phases, each building on the last. A step was complete only when it built, passed its checks, and was committed to Git, so every step was recorded and easy to roll back. I logged every decision in the plan with its date and reasoning.

Stage 1, Foundation: phase 1 setup and design system, 2 data layer, 3 core UI, 4 persistence
Stage 2, Features: phase 5 saved and search, 6 size modes, 7 feet and inches, 8 feedback
Stage 3, Polish: phase 9 UI polish, 10 onboarding, 11 accessibility
Stage 4, Launch: phase 12 naming and store assets, 13 account and website, 14 launch

My working setup

Claude Code and the iOS Simulator sat side by side. I followed the detailed steps in the project plan: Claude built each one, and I reviewed it and gave feedback. Once a step was solid and ready to move on, it was committed. Each session covered one or two features and took about an hour.

Claude Code, the project plan and the iOS Simulator side by side on one screen

Three kinds of testing

I used three kinds of testing: Claude ran tests, reported errors and gave recommendations; I tested in the Simulator on my desktop; and I tested on my phone. I gave Claude detailed feedback in text and visuals to fix the details.

My desk: the Simulator on the monitor and the app running on my phone in front of it

App Store Launch

Once the build ran smoothly in the Simulator, I turned to a new area to learn: Apple’s app launch process. I enrolled in the Apple Developer Program, then worked on the app name, keywords and store preview images. After I submitted the app, App Review asked for more information, including a demo video. No bugs were found, no code changes were needed, and the app launched a few days later!

The app's App Store listing on a Mac, with the icon and five store preview images

Effort & Lessons Learned

Overall, I spent 62 hours from idea and product requirements to building, testing and App Store launch. Coding took the largest share, but more than half the time went into the product, design and launch. Through this exploration, I learned new tools, new ways to design and build with AI, and more.

Donut chart of hours by phase, 62 hours 48 minutes in total from idea to launch
Hours by phase: Concept and PRD 7.5 hours (12%) with Claude; Design 17.4 hours (28%) with Claude Design and paper sketches; Code 27.5 hours (44%) with Claude Code, Xcode and the iOS Simulator; Brand and store 6.5 hours (10%) with Claude Design and Claude Code; Launch and review 4 hours (6%) with App Store Connect and TestFlight
  • Have a plan, don’t rush into details

    Defining a strategy and making a plan before jumping into details has always been one of my strengths. Taking time to plan and define an achievable scope makes the process efficient and avoids duplicated or throwaway work.

  • Adjust quickly and focus on the big picture

    Things don’t always turn out as planned. New challenges and ideas come up along the way. Focus on the big picture, and react and adjust to keep moving forward.

  • Embrace the unknown and ask questions

    I knew the tech workflow only at a high level, so I asked Claude and learned the right process. It’s OK not to feel confident about or understand every detail. Focus on the process, the results, and making a good product that users like.

  • Marketing matters

    As expected, the app didn’t go viral or reach the top of its App Store category. But I also realized that with hundreds of similar apps on the App Store, marketing strategy and effort are essential to gaining visibility and traffic.

What’s Next

For this app, I’m monitoring the App Store analytics and using the app myself to note improvement opportunities. I also plan a next version that adds features and enhances the accessibility I didn’t build for the initial launch. I’ve learned a lot from building and launching this app, and I’m looking forward to turning my other ideas into reality.