I work on mobile native applications.

Without an active harness (eg. Appium) that can end-to-end deterministically verify the changes you make continue to work correctly it is almost impossible to continue to keep the same pace on the app.

Unsupervised LLMs (even fabel) are categorically incapable of running parallel unsupervised mobile app feature development.

That is my personal, first hand experience working in a team in this space.

What you are (I guess?) experiencing is user-in-the-loop light touch LLM development where you can 80% most tasks quite quickly (much faster than without assistance!) with a small number of human developers working on largely unrelated features and manually verifying they are correct and manually fixing the platform specific issues you encounter.

Maintaining a strong appium end-to-end test suite is still extremely challenging with notifications and maps.

Honestly, it blows my mind you could even being to claim that of all things, native apps using obscure languages like swift are suitable for this, compared to the much much easier path of web + react.

You might say “yeah yeah, but one month? Come on!”

…but have you actually seen how much code fabel can write in a month?

Its a lot.

So sure, you say, work at a slower pace. Don't just endlessly run a frontier model in unsupervised feature development mode.

Yes… you see, thats the point. Thats what the op is saying.

Move more slowly, and you can avoid building a spaghetti castle (ok sure! If you dont wanna, maybe don't retype every character by hand, but the point of that practice is not upping your wpm typing speed. :p It is to take the time to think, design and collaborate, not rush rush rush)