AnAngryAlpaca

It could be a cost issue. A chip that collects data from connected sensors and sends it via Wifi is small and cheap. Adding a display and buttons ads size, complexitiy and costs. Therefore manufacturers offload the interface to an app and a device you already own, and they can update without expensive recalls.

If the task or device is more complicated and the device would also need it's own storage, CPU, display, sound etc. the product costs could go up by hundreds of dollars, depending on functionality and how many units they plan to ship.

I also hate apps. Still have my 2010 smartphone in a drawer that still turns on, however it;s useless because google playstore, maps and email now used an more modern SSL standard that this phone does not support anymore, and it won't receive any updates. I expect the same will happen to a lot of devices that are controlled by apps when the manufacturer decides he won't support it anymore, or Google breaks the app because some new protocol must be supported now that didn't exist 2 years ago when the app came out.

To be valid, the email just has to match [anything@anything]. ,🙃@localhost can be perfect legal if localhost supports utf8 in usernames.

I see you never worked in a developer team. My current boss once in 1995 opened a geocities page about someones poodle and favorite girl-band. After 3 minutes on that page he proudly declared "I now know everything there is to know about HTML and user interface design, and never have to see another website ever again!"

Since then, he is making designs, and the tiniest amout of criticism or improvements ("maybe we should have a placeholder telling users what format we expect here.", "Can we use a date-input instead of a textfield here?") is shot down with a 5 minute yelling how "the users just have to learn this" and "we always have done it this way!" or "if the user is too stupid, he should read the manual" (which is incomplete and still features windows XP+IE6 screenshots). There is an option in the bug tracking system which says "user error/user training required", but if you read it it's really all huge usabillity issues because people cannot figure it out, and the system has no helpfull error messages...

The thirteenth floor was a (pretty good) remake of the German 1970s movie "Welt am Draht".

Try opening your subscription page as usual with your ublock, but then right-click "open in private window" the videos you want to watch. Works for me.

People seem to forget that there was a time before cars, where people had to rely on public transport alone.

Most people live in a city. In Australia and NZ it's around 90%, in China, Europe and Canada for sure over 50%.

Sure, but withg wechat you can link each user to the real person, bank account, phone number and find his friend circle on we chat. This might not work so well on other apps where any user can sign up via vpn and a random email address...

That is a good example, but as the other commenter pointed out I dont think you can compare weChat with Twitter. Twitter is a startup trying to make money from it's service. WeChat is a tool for the chinese goverment to track each persons chats, money transactions and purchases, and as such will pretty much receive all the funding it needs. Being profitable is not the main objective of WeChat.

I dont think an "everything app" will ever work.

You can make one thing that does one thing very well and better than the competition, and you will get users. Or you can do one thing that will try to do 10 things half assed, and it will fail to impress users. This happens because you have to divert your resources (time, money, people) for development, maintenance, new ideas, design etc. across all your "everythings". The more everythings you have, the less resources each one gets, however the costs for maintenance, bugfixes, updates etc. stay the same.

This happened to Yahoo in the early 2000s, where it tried to be Search, News portal, Email, Web directory, Weather, games and whathaveyou, however it failed because none of it's parts was better than the competition.

The better approach for an app would be to do it's own thing it is supposed to do, but support other apps that can enhance your product by allowing it to interact with outside data, and also give his data back out to other apps: use mailto:links/email instead of inventing your own messaging protocoll, support exporting to standard calendar files instead of implementing your own calendar that is oblivious to the schedule on the users phone. Support exporting datasets into common formats the user knows from his everyday tasks (excel, csv) so he can run his own data analysis on it, instead of baking some half-assed "analytics" module that only has 10% of the features the user needs.

With dark patterns you can "guide" the user to click a particular button, for example by having "accept" in a large, bright stand out colored button, and the "reject" button in a low contrast, small or disabled looking button.

This will not prevent people from clicking reject, but it shifts the percentage of people clicking accept vs reject in the websites favor.

Serious question: what's the deal with iHeartRadio? It seems like they are involved in podcasts and the local radio station, but I usually download my mp3 and don't use apps, so not sure what's going on there...?