> The problem is that while these tools can help you build a simple prototype incredibly quickly, when it comes to building functional applications they are much more limited
As someone with 0 (zero) swift skills and who has built a very well functioning iOS app purely with AI, I disagree.
AI made me infinitly faster because without it I wouldn‘t even have tried to build it.
And yes, I know the limits and security concerns and understand enough to be effective with AI.
You can build functioning applications just fine.
It‘s complexity and novel problems where AI _might_ struggle, but not every software is complex or novel.
do you make money with it? like monthly subscription?
because that's my achilles heel, how to synch the mysql backend with apple's payment system so it knows when user ordered or cancelled
The feature is shipped in the latest builds of claude code, but it's turned off by a feature flag check that phones home to the backend to see if the user's account is meant to have it on. You can just patch out the function in the minified cli.js that does this backend check and you gain access to the feature.
it's my repo - it's a fork of cc-mirror which is an established project for parallel claude installs. I wanted to take the least disruptive approach for the sake of using working code and not spelunking through bugs. Having said that - if you look through the latest commits you'll see how the patch works, it's pretty straightforward - you could do it by hand if you wanted.
If you really want to learn: Watch some people (your mom, neighbor or friends) use the app. Literally tell them "Hey look here's a new tool, can you set a couple of timers for me." and sit beside them and watch them use it. Don't tell them anything, just watch.
A minor note: Nowhere in the release note do you say what the app is or what it does. Sure, I can find out by following the links, but coming in cold not knowing what immich is, I was kind of expecting to learn that in the write-up.
Just a quick note – the "Configure Your Exercise" step was a bit confusing. It took me a while to figure out what “Number of Gaps” even meant, since that’s not something I’d usually think about configuring.
Also, choosing an input method felt tricky. I hadn’t used the product yet, so I didn’t really know what to pick or what would work best for me.
Once I got into the app, everything made sense, but it wasn’t clear upfront.
Maybe you could let people start with a default setup and explore the options while using it. That way, the learning happens more naturally and the config step doesn’t feel like a blocker.
If that's true then why include it at all? From a UX perspective you don't want to throw a bunch of configuration options at the user before they even know what the options mean.
It's a hurdle people have to take; and its eating from their 1.5second attention span. Some will get stuck or leave. OP asked for thoughts, this is to help him convert more people.
reply