4 ms·
I hate to mod this up, but, darn it, I have to mod this up. Web apps have pros and cons. Desktop apps have pros and cons. Desktop apps written with web-app tec
by mechanical_fish 19y ago
I hate to mod this up, but, darn it, I have to mod this up.
Web apps have pros and cons. Desktop apps have pros and cons. Desktop apps written with web-app technologies have... cons. The interface is limited to what the browser can support. There are more moving parts. You have to worry about synchronizing the data. You have to worry about pushing out upgrades. You have the same support costs as any Windows desktop app, and worse, because you're supporting a system that nobody else has ever seen because you wrote it yourself. Etc. Etc.
Of all your ideas, the Asus-eee one seems the best -- just make the customers buy hardware with the software preinstalled. If they screw it up, have them mail it in for a new one. If the eee gets discontinued, find another small OEM Linux PC and port the software over. If you go the vmware route you might as well be selling and supporting an installable Windows app, which you already are.
But the idea is still crazy. Customers are not stupid. They know the difference between a full-featured Windows app and a web app that has been crippled by cutting off the Web part. You're going to throw away all the advantages of moving to webapps in the first place, and invest mighty engineering effort, all to replace a Windows program with a program that (from the non-networked customer's perspective) does the same thing but with a different, feature-poor browser-based interface. That non-networked 25% of your user base is likely to respond by either (a) demanding that you continue to support the Windows version; (b) switching to a competitor's Windows- or Mac- or Linux-based product; or (c) buying some networking, and joining the other 75% of the customers. Once that process has shaken down, you'll be left holding an expensive, tricky Slingshot-esque technology that has almost no users.
- inklesspen 19y ago"Buying some networking"? I admit I wasn't exactly clear with what the app does, but in the iPhone section I did say the app has to be used in places where there's no cell phone service, let alone wifi. It's an app used by public health agencies, who _have_ to be able to visit clients in their homes and chart their progress. And plenty of homes in the rural US have no dial-up internet, no broadband, no wi-fi, and no cell-phone coverage, and no sign of that changing soon. That said, I agree with you. The decision-maker at this company doesn't, and as I mentioned below, I've got little leverage to change things.