I don’t see the OS providing a unified UI that allows people to write apps as services as a problem. I’m likewise confused about what you’re actually try to say here. You’re conflating your ideological stance with technical functionality as far as I can tell. It’s perfectly possible for an open platform to do the same things WeChat does, and that would result in a much better user experience than the current approach. I don’t know why it’s so hard for you to grasp this.
@yogthos They literally JUST banned and unbanned Tiktok at the whim of an annoying orange, and Twitter as we knew it is dead because of a rich billionaire.
You’re glossing over real problems in the name of good ux.
The client-server pattern perpetuates power imbalances, and “Super apps” make that problem much much worse.
It’s just something you keep repeating, but that’s just not true. Coupling the UI with the business logic of the application is a fundamentally wrong approach. It makes it effectively impossible to compose apps the way you can compose command line utils with piping. Apps should be designed as client/server by default, and then you could always leverage the service API for the app any way you want, slap a custom UI, use it in automation scripts, etc. It’s just way more flexible that way.
@yogthos Nobody in their right mind couples UI to business logic, we have MVVM for that and it enables some very impressive integration and UI switching in apps.
However, thinking at the application level is ignoring everything I just said about the ways that apps communicate.
Both Android and iOS are very much a walled gardens last I checked.
@yogthos Right so are you saying we should make the problem bigger?? I’m confused what you’re trying to say here
I don’t see the OS providing a unified UI that allows people to write apps as services as a problem. I’m likewise confused about what you’re actually try to say here. You’re conflating your ideological stance with technical functionality as far as I can tell. It’s perfectly possible for an open platform to do the same things WeChat does, and that would result in a much better user experience than the current approach. I don’t know why it’s so hard for you to grasp this.
@yogthos They literally JUST banned and unbanned Tiktok at the whim of an annoying orange, and Twitter as we knew it is dead because of a rich billionaire.
You’re glossing over real problems in the name of good ux.
What does this have to do with anything being discussed here.
@yogthos Everything, this entire thread and several others that people have started with you.
It’s worth saying twice:
The client-server pattern perpetuates power imbalances, and “Super apps” make that problem much much worse.
It’s just something you keep repeating, but that’s just not true. Coupling the UI with the business logic of the application is a fundamentally wrong approach. It makes it effectively impossible to compose apps the way you can compose command line utils with piping. Apps should be designed as client/server by default, and then you could always leverage the service API for the app any way you want, slap a custom UI, use it in automation scripts, etc. It’s just way more flexible that way.
@yogthos Nobody in their right mind couples UI to business logic, we have MVVM for that and it enables some very impressive integration and UI switching in apps.
However, thinking at the application level is ignoring everything I just said about the ways that apps communicate.
Pretty much no app provides APIs to access the business logic layer outside the UI. You’re just trolling at this point.