Re:Microsoft Teams 2 will use half the memory, dropping Elec...
by chrisseaton on Saturday June 26, 2021 @11:21AM
(#27642651)
> the user generally gets an experience that is similar to other native applications
This sounds like the goal you want to achieve using native as a tool.
But anyone who struggles to grasp non-native UI and UX is going to struggle to interact with the modern IT environment as there is no standard for web-apps.
Re:Microsoft Teams 2 will use half the memory, dropping Elec...
by ptx on Saturday June 26, 2021 @04:10PM
(#27645388)
If I order a cup of tea, you could argue that what I actually want is to achieve the goal of drinking something which has the taste, smell and general nutritional profile of tea.
Theoretically, there might exist a cup of coffee that achieves this goal. But I've never seen one, and if you serve me coffee it's almost certainly not going to achieve my goal.
"Native" is the implication that a certain level of comformity is present: the user generally gets an experience that is similar to other native applications.
As you develop with native APIs, and when you follow the best practices for the platform, you end up with a product where the UX is much easier to grasp for the user. Non-native solutions very often have different UI/UX patterns, which leads to users having to learn these patterns before the application becomes understood by them.