Totally agree and basically is destroying the software economy that we have, because it feels that everyone can make their own app, suiting their own requirements. But they don't realise this to be a trap, because the majority of the effort of any product is the ongoing maintenance and evolution. Let it a new browser version come along, a new OS version, a new LLM version and once their "tuned", self-made app suddenly stops working or misbehaving, they will realize that it ain't so easy as promised, even if the LLM can be used again to evolve it.
But as all major breakthroughs, the path is forward and there is no logic argument that you can make to let people consider otherwise. Eventually, all the dust will settle down and it will be easier to uncover this and other misconceptions, until then, no worth trying to convince people otherwise.
Copywriting is fundamental for any app's user experience and yet, it is one of the most neglected aspects of modern's app design.
Part of this is due to the difficulty of managing an apps's strings using old-fashioned methods, such as editing strings or XML files, at least for Apple and Android platforms. I felt this as a big painpoint for all the apps that I work with at work. Once an app grows into hundreds or thousands of strings, it becomes very difficult to manage them.
While the task of auto-translating to other languages (localization) is pretty much solved with AI tools, the baseline language still needs a human-in-the-loop, to make sure there are no typos, the tone is appropriate, and the text is understandable by the user.
That is why we built an app for that — Strings Reviewer — to review the baseline language strings, organising automatically the file with sections, making it easy to proofread, quickly search for specific strings, and if you want, you can also auto-translate new strings to other languages.
Disclaimer: there are other ways for managing your app's copywriting. You can use TextEdit, Xcode, Android Studio for managing strings directly, or if you want a very complex and expensive online solution, you can use something like Lokalise. This native macOS sits in between those two extremes in the spectrum: an app for the rest of us, to make localization easier and without too much fuss.
I built UI Playground, an iPhone app for browsing and experimenting with iOS UI components.
The idea came from wanting a simple way to explore UI patterns and components individually instead of digging through sample projects or documentation. The app lets you quickly look at different components and interactions, which can be useful for learning SwiftUI or getting inspiration when designing mobile interfaces.
I mainly use it as a reference when prototyping or experimenting with UI ideas.
But as all major breakthroughs, the path is forward and there is no logic argument that you can make to let people consider otherwise. Eventually, all the dust will settle down and it will be easier to uncover this and other misconceptions, until then, no worth trying to convince people otherwise.