3 ms·
I don't understand... All these things are possible in systems where no such separation exists. What happens in other systems is that you can ask the system fo
by inglor 6y ago
I don't understand... All these things are possible in systems where no such separation exists.
What happens in other systems is that you can ask the system for an accessibility tree (for instance) and get a DOM like tree (for example in Android) so stuff like screen-readers still works just fine.
Ditto for contrast - all these things are possible if the platform builds its building blocks with them in mind and the users don't have to deal with it.
All the things and use cases the post mentions are possible in flutter/dart, Android and iOS.
The thing preventing you from "sticking your app in Google Translate" isn't your app in iOS/Android/whatever or the technology - it's Google/Apple.
- swiley 6y agoThe nice thing about the web is that when a page does something stupid or malicious the user can inspect and modify the tree on their own.
- inglor 6y agoThe thing making this easy in web pages is the _tooling_ though. The reason this is harder in Android than in web environments is that web tooling is just _very_ mature. Theoretically nothing is preventing you from exposing this functionality in Android/iOS/flutter/react-native/ whatever. In practice hot-reloading is a lot more valuable and useful since you edit from your IDE (and not the devtools) and all modern UI platforms (flutter/android jetpack/SwiftUI) support it from what I recall.
- swiley 6y agoIs it tooling? I think it's a culture thing. With Android/iOS/flutter/react-native there's an expectation that developers are a separate community from the rest of the users, one that might not even use the apps they right daily. This contrasts heavily to the web where the users and developers are often using the same tools.