I need to be enlightened about the use cases of Urbit. I don't get it.

Video artist. Insatiable sense of curiosity. /cars

What I as layman understand: 
1. Enables the equivalent of taking your hdd from one computer and plugging it into another and all apps/network continue working as if nothing happened. You own not only your data but also the software that interacts with it.

product/design/UX exploring web3 🌐 nf.td/mario — ~sigmes-modfyn

2. In theory this allows network service models that rely less on centralized "megacorp" services. Yes, someone still needs to keep the computer/server plugged in, it could be you or third party you trust. And if you decide to leave you leave with everything not just plain html/docs that another platform can't take it

There are leats 2 different apps/ux layers at the moment: those from tlon.io and those of holium:

There are leats 2 different apps/ux layers at the moment: those from tlon.io and those of holium: https://twitter.com/HoliumCorp/status/1699840718775123988?s=19

If you just focus on the UX/UI layer though, right now it is kinda like slack with document and gallery channels for tight nit groups

Not at all. I'm not technical but my understanding is that with dapps you decentralized a small (albeit critical) part of the app. And public blockchains like Ethereum are slow in computing compared to urbit.

Ahaa

I appreciate you laying it out! Urbit does sound intriguing, but still curious about how building on Urbit differs from creating DApps on Ethereum? Is that a dumb question?