4 ms·
It's likely you're underestimating the complexity required to run Hopper and support all existing features. Only a small subset of those engineers will do mobil
by carb 5y ago
It's likely you're underestimating the complexity required to run Hopper and support all existing features. Only a small subset of those engineers will do mobile work. And they likely have many more priorities than building Auto-buy, the benefits and viability of which isn't obvious. So while the rest of the Hopper Eng team churns on with other long- and short-term changes, one or two engineers may have been able to lobby for a POC on iOS. Or maybe it was just a quick week long hackathon project that's still being monitored for ROI.
- throwaway823882 5y agoSomething is potentially wrong. Saying "we only have 100-200 engineers, we can't get around to making a website" is a terrible excuse that points to mis-management. It doesn't take more than a couple developers to put together a basic "shopping for flights" web interface. If they have a backend that serves iOS, it should have a REST API, so slapping a web interface on that shouldn't be a big deal. But it's also possible that it's like someone else mentioned: "if the product is free, then you're the product". Maybe they just don't care to get more customers/solve their problems, because they are harvesting enough data about iOS visitors to make a profit. If they don't want any more customers, then nothing is wrong.