It makes sense. Just like "economy" vs "first class" for travel. As a business, it needs to partition out the consumer buckets into various groups for profit maximization.
For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
It's almost disheartening that there are folks out there that like the clump, cluttered busy mess that is sourcehut.org over the clean, beautiful design of the Stripe website.
For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
My family has ordered online from all three of these retailers during this pandemic. Walmart and Target may have roots in traditional retail, but their online pipeline is quite robust these days.
I'd rather use a native app than a PWA any day of the week. The experience of a mobile web app is clunky, slow, typically ugly, and just a generally bad experience.
Essentially all of the events you mention plus a good amount more are either in an active product development pipeline for vendors we work with or are actively being worked on internally on devices we are building.
It's a tough space.. margins on these hardware devices are thin already, and sometimes negative as they are simply loss leaders hooking in users for long-term saas payments, so in our case, it's cheaper to build it in-house.
I'm in the industry and I have to agree here. All of the devices we develop and use (third-party) either already have this capability built-in to the device or are working on it right now.
what about code review? And if the answer is that everyone at the company is a rock star and doesn't ever need code review, then I'll be at a loss of words.
I'm currently at a company where our iOS product has millions of paying customers. FWIW:
We run a flavor of the coordinator pattern + MVVM. We use delegation to handle messaging between view models and view controllers. Services are currently handled by a super ugly singleton, but that's a by-product of legacy architecture. New features usually inject the service directly into the view model.. and there has been some talk in potentially moving the service to the coordinator to mimic a unidirectional data flow.
The issues you mention, i.e. globals, lack of unit testing, fat view controllers and lengthy functions... none of that stuff, if included in a pull request, would pass our code review. So generally we self police each other to avoid code smell.
Easiest way to cut through the noise is to give candidates some whiteboard questions. This will invariably filter out some good candidates that aren't good at these problems, but you'll be left with a bunch that have some baseline competency.
I still don't know why DropBox is a thing. For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
I do, but more so the era in which I heavily used it. I started a local IRC channel for my high school. Word spread and eventually we had 100-200 people on it every single night, which was a non trivial % population of the entire school. Not just nerds... everyone from all groups was on it. People are school were asking the more tech friendly folks: "How do I get mIRC on my computer??"
There were so many people on it that there was a legit problem identifying who was who (i.e. nicknames != real names). I eventually made a page linking IRC nicknames to profiles.
Looking back on it now, if I had had more vision, in a parallel universe, I would have replicated this experience to other areas schools in the region.. then state, then country then....?
native, all the way. launch on one platform. get traction? fine, scale to multiple platforms and at that time evaluate whether you should move to a cross platform framework (i.e. react)
This is an anecdotal datapoint that is insanely useless in the real world, but the fact that it is the top comment is typical of this site.