Hey X đź‘‹
I'm 50 and I've been writing code for a living for 25+ years.
Along the way I've built a lot of side projects. Small SaaS tools, Amazon affiliate sites... some made a little money, all of them taught me something.
Now I'm going all in on iOS apps, on evenings and weekends, in between being a husband and dad of 3 here in Michigan.
→ 3 apps on the App Store
→ 1 in the works: StrengthBuddy
→ Goal: $30K MRR
I'll be sharing what's working, what isn't, and everything I learn along the way.
If you're building too, let’s connect 🤝
I decided to test Gemini 4 Hydrogen and Neon API calls against GPT-6.1 Terra for an app I'm developing.
The two new Google models are not even close to being competitive, either in terms of cost or quality of results.
43
Hey everyone! I’m building StrengthBuddy, an iOS workout builder and tracker for strength training.
I know it’s a crowded space, but I haven’t found an app that fits how I like to train. So I decided to build one for myself and see if it clicks with anyone else.
The idea is simple: an AI workout builder creates your program, and a quick logger lets you record exercises, sets, reps, and weight without getting in your way.
I used to ask Claude or ChatGPT to build me a workout plan, then enter it by hand in a separate logging app. A lot of AI fitness apps update your routine day to day or week to week. I prefer to stick with a consistent weekly routine and focus on progressive overload.
If you were setting up a program, what would you want the workout builder to ask you? Here’s what I have so far:
- Training goal (hypertrophy, strength, powerlifting, longevity, etc.)
- Training experience
- Areas you want to focus on (like shoulders or glutes)
- How many days a week you can train
- How long you have per session
- Preferred workout split
- Equipment you have access to
- Preference for machines or free weights
- Exercises you want to include or skip
What’s missing? Is there anything here you’d rather skip?
Most of my apps have just been launched (or relaunched) in the past year, and I’ve been putting off testing them on the iPhone Duo for two reasons.
First, they all still have relatively low download numbers and are probably only being used on a handful of Duos, at most.
Second, I was afraid they would lay out poorly, which would pressure me to go back and start fixing them, stopping momentum on what I’m currently developing.
I started testing them in the simulator and so far, I’m happy with the results.
It’s encouraging to see that my decision to start with native SwiftUI as a platform makes them “not terrible” by default. I’ve been hearing some complaints about apps like MacroFactor (built with Flutter), and I don’t envy what their team has to go through as they navigate some of Apple’s decisions around layout and reflow on the Duo.
I don’t love the way the accessory toolbar presents as a long, horizontal area along the bottom, while the toolbar is over to the right (see image 3), but it could be worse.
3
1
107
Replying to @PeterMcCormack
It's not the materials, ok... it's the design. You're paying for design.
1
29














