3 ms·
I think the downsides associated with having a common codebase are grossly underestimated. It inevitably leads to compromises for which a native UX would have b
by reilly3000 5y ago
I think the downsides associated with having a common codebase are grossly underestimated. It inevitably leads to compromises for which a native UX would have been superior. Speed, layouts, native idioms, and continuity come to mind. Sure it’s a lot to ask for a truly native Android app to keep parity with a truly native Mac desktop app, but compared with a React Native codebase, the experience is sublime and the fussy platform shims aren’t needed.
- bsder 5y ago> I think the downsides associated with having a common codebase are grossly underestimated. I don't. Event loops, for example, work completely differently on macOS, iOS, Android, Windows and the Web. You will abstract across them eventually and you will get that abstraction wrong unless you are a programming god--at which point you might as well just use a cross-platform system to start. The cross-platform guys have big companies with lots of money and programmers solving problems that you haven't even dreamed of. If you're releasing on multiple platforms, you will not win.
- pantulis 5y agoI guess you need to decide what indicator are you trying to optimize: user experience vs cost effectiveness. Evernote's CEO decided for the latter and I believe he's right betting the company on the Electron based clients. This is also understandably infuriating existing users as they lose the biggest feature that was the native feeling of EN. Other features are being slowly added along with some new ones that are arguably useful, but snappiness will not come back.