I don't understand the rant. So BMW's smartphone app is flawed. Meanwhile my 2005 Prius has keyless entry that simply works and last a several years per battery change. It's single purpose and only works when very close to the car.
80% of the author's frustration could be resolved with a lockscreen widget that launches the app into the appropriate action, preferably authenticated with fingerprint/TouchID/passcode.
Then it becomes a) pull out phone, b) unsleep display c) use lock screen widget d) authenticate using passcode/TouchID.
While the BMW example is easy to pick on, I am skeptical that the book deserves to be a book. In my opinion, the best book is no book. I'm quite tired of books that are overgrown 1 page essays.
>Then it becomes a) pull out phone, b) unsleep display c) use lock screen widget d) authenticate using passcode/TouchID.
What if I want another widget on my screen ? Do I put it there too ? Where do I stop ?
And in any case, it is still longer than just a) pulling a handle.
The whole point of the rant is that interfaces shouldn't be something we have to go through: they should be transparent. In the case he presented (Siemens'), there is no interface.
We have built a culture of "there's an app for that" where 99% of these apps are absolute, total crap. You don't need Tapatalk's app to browse forums, you don't need an app to turn on your lights, etc. An unbelievable amount of apps are actually slower at doing something than they were supposed to solve.
80% of the author's frustration could be resolved with a lockscreen widget that launches the app into the appropriate action, preferably authenticated with fingerprint/TouchID/passcode.
Then it becomes a) pull out phone, b) unsleep display c) use lock screen widget d) authenticate using passcode/TouchID.