4 ms·
I keep fighting with devs that want to use web-everything. Luckily for me, i have the ultimate power so i can just say "Firefox doesn't support that. I don't u
by monegator 11mo ago
I keep fighting with devs that want to use web-everything.
Luckily for me, i have the ultimate power so i can just say "Firefox doesn't support that. I don't use chrome. period."
But lately i had to start saying Safari doesn't support that so we would lose all iphones, or we can start investigate after we have a working solution. God damn react.
- prox 11mo agoIt’s such a mess isn’t it.
- albinn 11mo agoOut of curiosity, what are you proposing instead? I'm currently working in a small company (less than 4 full time employees). And while we can never support native apps for all the platforms I have been wondering what we would use instead of a web app? The advantage of the web app is that it just works, without installation, so there's no friction there. I'd very much prefer a native app, but the overhead is quite high, no?
- dickersnoodle 11mo agoDepends on the app and how it's built. There are ways to architect native mobile apps that give a lot of flexibility, and there are even ways to build both the native and web apps that help with information architecture and UX consistency but you have to design them with that in mind.