Portal Windows for Electron
blog.tandem.chat
Portal Windows for Electron
1–10 of 52 posts
Re: Portal Windows for Electron
#2Re: Portal Windows for Electron
#3Re: Portal Windows for Electron
#4Why not just write a native application?
- Easy cross platform support
- Singular language/framework (typescript/react) for everything you're doing
- Can share a lot of components/logic with mobile apps if you use React Native
Re: Portal Windows for Electron
#5Why not just write a native application?
Re: Portal Windows for Electron
#6Why not just write a native application?
Here's a few very valid reasons imo - Easy cross platform support - Singular language/framework (typescript/react) for everything you're doing - Can share a lot of components/logic with mobile apps if you use React Native
Re: Portal Windows for Electron
#7Earlier quoted context omitted.
Here's a few very valid reasons imo - Easy cross platform support - Singular language/framework (typescript/react) for everything you're doing - Can share a lot of components/logic with mobile apps if you use React Native
- you want to make sure that people respect the importance of your app by not running it along with everything else because it needs 10x the amount of resources a native app would
Re: Portal Windows for Electron
#8Why not just write a native application?
I'm not excusing it, I curse Slack every day I have to use their Electron app (though mostly just use it in a browser tab now) but we have this exact same conversation every time anything about Electron is posted on HN. None of the parameters for making the choice have changed since the last time we did.
Re: Portal Windows for Electron
#9Why not just write a native application?
Here's a few very valid reasons imo - Easy cross platform support - Singular language/framework (typescript/react) for everything you're doing - Can share a lot of components/logic with mobile apps if you use React Native
You get substandard desktop applications that tend to frustrate people who are deeply immersed in any one ecosystem and expect native applications to have deep integration with each platform and comply with each platform’s design sensibilities.
But history shows that applications written against cross-platform toolkits have done just fine, as have applications that completely embraced “going native” on particular platforms.
I’m left with the thought that either strategy works if you go “all in,” the mistakes come from:
1. Going cross-platform but then doing ridiculous back-flips to try to make the app feel really, really native. Just take what the platform gives you, and accept that you’re giving people a web-like experience that happens to have some native affordances. Learn to live with the few complaints from retro-grouches.
Or, 2. Going native, but skimping on deep integration and fully embracing the look and feel of each platform. This is one of those “penny-wise, pound-foolish’ strategies: You ship faster, but you lose the big benefits of a cross-platform tool, and you don’t satisfy the users that appreciate what a native app offers in look, feel, and integration.
Re: Portal Windows for Electron
#10Earlier quoted context omitted.
Here's a few very valid reasons imo - Easy cross platform support - Singular language/framework (typescript/react) for everything you're doing - Can share a lot of components/logic with mobile apps if you use React Native
- you want to make sure that people respect the importance of your app by not running it along with everything else because it needs 10x the amount of resources a native app would