> I suppose it depends on what you mean as a growing app. A few of the examples are apps that you could easily sell as a freelancer/contract work.
The examples are interesting but what I don't see in your docs is how to control UI. Is that driven entirely by data types? What happens when an app wants/needs novel UI/flow?
Off-topic: Your platform looks like a really interesting tool for rapid-prototyping. How do you see in growing with the needs of the app?
Also, what is the obsession with a single file? Before I get to 1,000 LOC, I'm going to be looking to split it up into logical pieces—one for the DB setup, one for the UI, etc.—just to maintain sanity.
I have serious concerns about any browser that requires a user account. I understand it drives the sync feature, and that they Take Privacy Seriously™, but I can't even test drive it before I commit to an account? That's a terrible onboarding experience.
And what if I don't actually care about syncing at all, or just don't trust an early stage startup that hasn't figured out monetization yet.
I do appreciate innovation in the browser UI space. But that's a hard pass.
PHP is _not_ Web only. You can write CLI tools and server scripts with it. Look at Composer. That is pure PHP.
PHP is a highly marketable skill. WordPress, with their mission to power 50% of the Web, is PHP. Not to mention … the Book of Faces.
There are modern frameworks for PHP like Laravel that play the same role as Django.
But, if you're learning a new language, why not JavaScript? Everything is JS now—server side scripts, full stack Web dev, "Internet of Things." It is well on its way to Total World Domination.