4 ms·
I think you would end up writing applications that look native, but not behave in a native way at all. We have a lot of those already. Just some thoughts: - fo
by moring 5y ago
I think you would end up writing applications that look native, but not behave in a native way at all. We have a lot of those already. Just some thoughts:
- for an application that modifies files (e.g. a text editor), are changes applied to the file immediately or is there a separate "save" action? Platforms differ on this. Basically your internal data handling becomes platform-dependent.
- define a set of keyboard shortcuts that is consistent and intuitive, but plays well with the platform's shortcuts. You'll basically define a separate set of shortcuts per platform.
- whenever functionality overlaps with existing native applications, cooperate with them instead of duplicating their functionality (especially in an incompatible way)