gitgud

Sorry mate, a lot of this is vibe coded. Thanks for taking the time to check it out though

That is a typo sorry (half-baked) reminds me of a bakery!

Well since nobody is suggesting it, then I will.

Go full native for each platform. React Native and Flutter are great (I’ve used them both), but there’s several reasons not to choose them anymore

1. Complexity - you’re adding another layer between your app and the device, debugging, compilation, device quirks all become much more annoying

2. AI coding makes it easier - This works both ways, flutter and react native become easier to develop, but so does native development

3. Support is always better on native - consider any issue you have building an iOS app, now add in React issues and then React native issues and then a bunch of other framework version issues… it’s generally better support if you use the tools the platform expect you to use

4. Code reuse is not as big of a deal as you think - trying to share UI code across android, iOS, web ends up making all platforms you build for worse, as bugs and performance issues go to all platforms… if you have a simply designed app, then a native experience is always preferable by users

I gave it a shot 4 months ago. 150k GitHub stars, it must be worth trying at least right?!… turned out to be some of the buggiest and clunkiest software I’ve ever used…

The idea of “your own agent instance that you can link to anything” has merit, but it was just so annoying to configure and actually quite expensive when linked to OpenAI (a few dollars a day to do nothing) also seemed to be a never ending stream of happy-baked vibe-coded features being merged… the whole project just gave me the ick

My initial thoughts are Cursor is already generalised to build all software, and Games are just a subset of all software. So it’s probably good enough.

Also point 3 “No money in gaming” is probably the main factor. There is orders of magnitude less money in gaming, than in SAAS. Think of how much money businesses pay for even basic software.

I’d also say performance is so critical and specific to every game, that getting AI to manage & architect it is fairly difficult (slop kills performance). This is nowhere near as big of a concern for most SAAS (slop friendly)

Even with all these reasons, I still think it’s worth trying to build!

Same legal system, but an OpenAI enterprise contract is not the same as a ChatGPT pro subscription... The terms of service agreement would be quite different

If you have an enterprise contract with them, the legal protections for the consumer is much higher… is what I’ve been told anyway

Pure vibe-coding isn’t that satisfying (as you’ve discovered) the problem is you’re constantly reviewing its huge output, and it probably goes wild in directions making assumptions.

It’s much more fulfilling to give the LLM guardrails by engineering the solution.

This means coming up with the high level architecture, dependencies, breaking down the system into deliverable chunks, and implementing those chunks. The LLM can help in all those steps of the process. And it will be much easier to review and keep an understanding of the code.

> The difference doesn’t matter until it does, and then it’s infuriating to work out what’s going on.

I love this quote, reminds me how annoying it can be when something isn’t reproducible locally… only in production…

I love this choice. As I began reading, it was immediately clear that it was deliberately written by the author, not AI marketing slop

I assume they signal what menu item does what, to make it less confusing on different screen sizes.

I.e. Large displays get “icon + label”, whereas small displays just get “icon”

Good UX abstractions out perform bad ones, which means they endure, are copied, and eventually become the implied standard UX… some examples of this are; the hamburger menu, tiny icons and auto-scroll for streaming text