4 comments

[ 2.0 ms ] story [ 23.3 ms ] thread
You also shouldn't build apps because people hate downloading them.

If you're app is for like a resturant, or store, you should instead go with a mobile site. One that has model-viewer capability. Those can run as standalone apps with Electron anyway.

That's what Spotify and other companies are doing.

Writing a native app exclusively is a bad idea unless performance is important.

1. You also shouldn't build apps because people hate downloading them.

2. That's what Spotify and other companies are doing.

Spotify provides both web and desktop version. Oops I mean three: web, desktop, and natime mobile. So, what can we conclude about this?

The take away is some people like downloading apps so if you can it might be a good idea to be effective with your time a design a code base that can be appified using tools such as electron. It's best to have as little code as is possible. This isn't to say don't write code, don't create anything because there will be some problems with it. Instead create as small a code base as you can while delivering the best possible experience.
Quote: "Whenever I have to come up with an example of a cheap app that performs poorly, feels clunky, and frustrates the user every time they use it, one particular app comes to mind. I won’t name the company...."

Yeah, I can. It's called Microsoft and is the main reason why I stopped using Skype, after like almost 2 decades of using it exclusively. Their Skype app is clunky, on both desktop (with that horrible responsive times due to their horrible implementation of ElectronJS) and mobile. Main reason to use an IM app on mobile is to have notifications fire up when you receive a message. Why Whatsapp /FB messenger / Signal can do this reliably and Skype is missing like 30% of messages? My wife, when we used Skype, had to actively open Skype to verify that she didn't missed my messages. Nowadays, hate or love Zucky, we use WA / FB mess and never had a single message notification missed.