@yogthos You misunderstand. If you make a “Super App”, you ARE making an operating system. Yes most OS’s have UX problems that prevent this level of integration, but the critical difference is that you’re giving complete control to a single entity.
The client-server pattern perpetuates power imbalances, and “Super apps” make that problem much much worse.
No, I don’t misunderstand. I’m explaining to you that the nature of this operating system is different because there’s a single unified UI backed by a bunch of APIs. The critical difference is that you have a unified UX that results in better user experience. It has fuck all to do with giving up control to anything. You don’t seem to understand the subject you’re attempting to debate here.
@yogthos No need to use strong language, I understand what you’re trying to say.
As a UX dev of over 10 years, UX is important but secondary to safeguards against being toyed with by power-tripping tech bros. That’s why I use fedi, that’s why I build with ipfs instead of http.
There’s nothing I need so bad that I would give up my digital freedoms.
I completely agree with you. This could be done at the OS level if everybody would agree on a common API. This what I’m trying to explain here, the concept of a unified UX experience is a net positive for the users, and it doesn’t need to be implemented as an app. Let’s not throw the baby out with the bath water.
@yogthos Windows 8 made a legitimate effort to provide unified OS-level APIs that apps could hook into and deeply integrate with. The “People Hub” was easily the best example of this, plus Charms, Settings integration, etc.
Everyone hated it because they didn’t understand it.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
@yogthos You misunderstand. If you make a “Super App”, you ARE making an operating system. Yes most OS’s have UX problems that prevent this level of integration, but the critical difference is that you’re giving complete control to a single entity.
The client-server pattern perpetuates power imbalances, and “Super apps” make that problem much much worse.
No, I don’t misunderstand. I’m explaining to you that the nature of this operating system is different because there’s a single unified UI backed by a bunch of APIs. The critical difference is that you have a unified UX that results in better user experience. It has fuck all to do with giving up control to anything. You don’t seem to understand the subject you’re attempting to debate here.
@yogthos No need to use strong language, I understand what you’re trying to say.
As a UX dev of over 10 years, UX is important but secondary to safeguards against being toyed with by power-tripping tech bros. That’s why I use fedi, that’s why I build with ipfs instead of http.
There’s nothing I need so bad that I would give up my digital freedoms.
The is a non nonsequitor, because having a single UI framework has little to do with power tripping tech bros.
@yogthos I’m not even talking about UI frameworks anymore, but the UX and client-server or distributed models that you’d build with them.
You can’t build a super-app without also creating a massive power imbalance.
I completely agree with you. This could be done at the OS level if everybody would agree on a common API. This what I’m trying to explain here, the concept of a unified UX experience is a net positive for the users, and it doesn’t need to be implemented as an app. Let’s not throw the baby out with the bath water.
@yogthos Windows 8 made a legitimate effort to provide unified OS-level APIs that apps could hook into and deeply integrate with. The “People Hub” was easily the best example of this, plus Charms, Settings integration, etc.
Everyone hated it because they didn’t understand it.
Meanwhile, WeChat managed to do it in a way that everybody loves.
@yogthos Doing inside an app is easier and significantly more of a power-grab.