Been quiet for a minute. Heads down shipping 🚀
Atey20 is now live on the App Store!
We built this because every fitness app assumes you meal-prep chicken & rice 24/7 and can drop $100+/hr on a trainer. Real life? Sometimes it’s Chipotle. Sometimes you’re busy. Most people don’t have that budget.
Atey20 fixes that.
• AI generates your realistic 12-week body transformation preview
• Meal plans that are actually sustainable: 80% home cooking, 20% your favorite restaurants & takeout
• Workouts customized to your goal, equipment, and schedule
Free: See your transformation preview instantly
Pro: Unlock the full meal plans + workouts to actually get there
Early days, small indie team. We’re all ears. Reply with what features would make this your daily driver. Can’t wait to see your Week 12 results 👀
iOS only for now (Android coming soon if we get traction 🙏)
Link: https://t.co/RlReII533B
@grok
#BuildInPublic #IndieDev #FitnessApp #AI
@nikitabier It’s hit or miss. Got lucky earlier this month with an update making it through the same day. Fingers crossed as we submit a big update today 😬 … on average it’s been 2-3 days though
@aakashgupta This is a good point. That’s the basis of what we did with showing our users how their body could look in 12 weeks. Helped them to visualize it https://t.co/pHj1F5CKbA
@Jason@grok Here’s our four frame image trend, it’s free to see how you can transform in the next 12 weeks, feel free to give it a try below @jason 🏃♂️
https://t.co/pHj1F5CKbA
built + submit over 20 times within 24 hours to test flight, before learning I could test locally on expo go and save time and money. deep learning lessons as I go… the irony of how vibe coding turns you into a coder if you stick with it and learn lessons #BuildingInPublic
When submitting your build to Apple App Store, if you get Metadata Missing for your subscription, save yourself hours by making sure you fill out localization at both the individual AND subscriber level #BuildInPublic
Nice site and great idea. I’d recommend giving a step 2.
For example your site provides ideas which is great and there’s a market for it. Likely though that a coder that’s ambitious enough to start a project, has ideas or pain points that they want to pursue. I think the true potential value of your idea comes at step 2 after the ideate phase is done, if you can help coders to extend the ideas that you help them create to get one step closer to a finished product
I think there’s a few ways you can do this:
- education: start by teaching or guiding them on how to setup GitHub, Vercel or Supabase.
- implementation: maybe charge $25 flat fee and create a micro service that literally walks them through how to do the listed above or automates the process
in a world where info is becoming abundant, the marketplace is looking to pay for having info explained or applied…
Overall a really nice site and I think regardless of whether you offer a step 2 or 3, your site will do very well as more traffic continues to come to it as SEO affects kick in 💯
the beginning stages of coding is tough. vibe coding is a good entry point but debugging and actually thinking through the flow is where it gets really tough. i think with the passion vibe coders ultimately (ironically) grow into amazing software engineers, as long as they don’t give up and continue to learn through the debugging and launching process
working with agents I feel the need to constantly reframe. as it’s easy to go granular, but I think that’s the danger zone. trying to build in a way that stays within the scope and features that were planned in the beginning is a challenge but it’s important because scope creep is real and it’s best to let users dictate feature enhancements early on … just some thoughts
Magic links were cool when I was doing PWA, but it became a headache when I wrapped. Now that I’m going to Native Mobile (maintaining PWA for SEO), I think socials & email/pw, may be a better option and skip the magic links. Using Supabase for Auth.
Any recommendations on this auth structure?