Our Story

The app is for people with an intersection of interests around health data and AI tools. First, people using the Apple Health App to track things, even better when adding in data around nutrition (Cronometer, MyFitnessPal), exercise, sleep, and various other metrics. Second, those people who are using AI tools to help them in their lives, work or otherwise, and wish to enhance how they interact with those tools in regards to health related topics and insights.

Here is how this app, project, and idea came about.

For the past several months, I've been in this mindset of learning — trying to understand the AI landscape, apps, tools, and what all of this means in this new working world and economy. I kept thinking of ideas for websites, apps, and tools, but mostly I was just exploring. I wanted to get my head around what was happening.

I kept explaining to my wife, "I'm just trying to learn as much as I can, experiment with these tools, and see if some of them can help me in my music promotion, education, marketing, or any of the other things I work on."

The idea for this app came from a pretty small but annoying problem: I wanted to export and analyze my Apple Health data. Doing that ended up requiring Claude to write a terminal prompt that could convert the Apple Health export file into manageable CSVs I could import into my health project in ChatGPT.

That health project idea came from Sam Parr (My First Million Podcast), who had mentioned that he used a "project" inside ChatGPT to track his health — basically using a chat-based, conversational approach to managing health tweaks and experiments with a lot of uploaded files for context.

At one point, Sam Parr and Greg Isenberg (Startup Ideas Podcast) talked about how if you find a pain point in your own life, maybe others have it too — and that's when it's worth trying to build something.

So, I asked Claude, "Do you think this terminal prompt could be turned into an app?" From there, "we" talked through the viability of the project, discussed features, did market research, searched Reddit and other forums for people with similar frustrations. I brainstormed names with Claude and ChatGPT, found one I liked, bought the domain, and then started thinking about design — the logo, the app icon.

The final logo and App Icon came from Sora (Open AI), an initial idea was started in Midjourney. Then I do remember needing to figure out how to create all the correct sizes for the App Store (there's a lot). AI helped me find the right tools. After a few failed attempts on random icon generator sites, I finally found one that worked via Apple itself (not sure why the Claude or ChatGPT didn't point me there first, but I found it eventually on my own). With a plan, a name, a domain, and an icon — it was time to start building the app.

I remembered hearing about Cursor on a few podcasts, so that's where I started. I had some direction from Claude, and a week or two before that, I had spent around 30 hours building a landing page for a music mixing and production class using Claude and Cursor. So I had maybe a few hours of experience writing HTML — but no real coding background beyond that.

Still, I dove in. I spent about a week iterating on the UI, fixing errors in Xcode, and refining features. At the same time, I needed a landing page for the app itself.

I remembered an interview Shaan Puri did with Guillermo Rauch from Vercel and v0. I thought, "I think that was all about building websites… maybe I can try it." So I did — hours and hours of back and forth between Claude, ChatGPT, Cursor, and v0. After about a week, I had a working website, a working app, and I was getting ready to submit to the App Store.

Around this point, I hit another major wall — DNS and email setup.

I needed Vercel to host my new landing page, but I also needed my existing email accounts to keep working. That meant separating DNS from the mail server and pointing my domain correctly. It took two days of back-and-forth between ChatGPT instructions, screenshots, and verifying every step.

This became a recurring pattern: I'd be told something by one AI tool, but what I saw on screen didn't match. App Store Connect had just been updated, so all the instructions I was getting were outdated.

My new skill became debugging AI itself — learning how to get it the right context, screenshots, or documentation so it could help me more accurately. I'd literally say, "How can I get you the correct information to guide me?" Every step — App Store Connect setup, Bluehost email configuration, screenshot upload requirements — required this constant verification process. I realized that for all the talk about "build an app in a weekend," the reality for someone with no experience is a lot more like learn everything the hard way, one misstep at a time.

There were multiple moments I wanted to quit. The app had been rejected multiple times by Apple. I was tired of re-uploading screenshots, updating metadata, and hunting down reasons that didn't make sense.

But every time I thought about giving up, I'd remind myself — this is what learning looks like now. I was building something real. I was experimenting with the same tools, reshaping entire industries. Even if the app flopped completely, I'd still have built and shipped my first iOS app from scratch using AI. It was frustrating. It was confusing. But it was also proof that the process works — just not as magically as people make it sound on podcasts.

The founders and builders I listen to — Sam Parr, Shaan Puri (My First Million Podcast), Greg Isenberg (Startup Ideas Podcast), Steven Bartlett (Diary Of A CEO Podcast)— make everything sound quick, clean, and easy. "Build an app in five minutes, hit 100K ARR."

I still don't fully know what ARR even means, but what I do know is that building something from zero — without experience — is possible. Just not easy.

There were so many times I had to stop and ask AI to define a term, explain a command, or show me what a menu looked like. Every day was a mini crash course in something new: Swift, StoreKit, HealthKit, DNS, Vercel, Markdown, GitHub, App Store Connect, and more.

I'm now on my second major revision of the app, with UI improvements and new features built in — all before the first release. I'm still waiting on approval as I write this, three rejections in and counting.

But this time, I'm not frustrated. I'm proud.

This started as curiosity and turned into the most immersive crash course in AI, coding, and the modern digital economy I could have asked for. I'm learning how to build, ship, and problem-solve in a world where AI is both the tool and the teacher. Even if the app never takes off, the process has already been worth it. This journey — from total beginner to shipping something real — has shown me that the new frontier of creation isn't about perfection. It's about participation.