4 ms·
Something occurred to me the other day with regards to integration, which mobile UX designers may or may not be aware of. What people really want is "Fat Cache.
by stcredzero 15y ago
Something occurred to me the other day with regards to integration, which mobile UX designers may or may not be aware of. What people really want is "Fat Cache."
Clearly, "thin client" was hyped and fizzled out, because it isn't quite what people want. They don't want a "thin client" to the cloud. A pure thin client is pretty dead when there's no network or the server's down. A "Fat Cache" would retain all of its functionality and the user's most used data. It would also have most of the advantages of thin client, namely invisible centralized administration. It would also ameliorate all of the disadvantages.
iCloud, Chromebook, and Kindle Fire/Silk Browser are all moves in this direction.
The focus of a computer user should be their data. This includes apps. The apps should also live in the cloud and just appear on all the user's devices. In fact, the user's application "session" should be in the cloud too. I should be able to start a session on a recipe app on my smartphone in the living room, then walk to the kitchen and just seamlessly continue my session on my tablet. No reopening the tablet version of the app, no repeating a search for the same recipe. At most, just one user operation to "open in tablet."
All these form factors should just be seen as interfaces to our data, just instances of a "fat cache."
- brudgers 15y ago>"iCloud, Chromebook, and Kindle Fire/Silk Browser" What do you do when the storm takes down your cable provider? Or when you are beyond your cell phone carrier's signal? And you have a project to get out the door.
- theatrus2 15y agoWhat do you do when the storm takes out the road, and you have a project to get out the door? If the "fat cache" still lets you work in a disconnected state (such as iCloud would let you), I don't see this as a problem.
- cryptoz 15y agoYou work on it locally, with your Fat Cache copy and your offline app. You sync up when the 'net comes back online. Should I ask you how you get your coding done when the power goes out? Either you don't get it done at all, or you write down ideas on paper. There's not much else you can do, and that's the way it is. Frankly, I've only had about 10 minutes of total, unexpected and unavoidable network downtime in the last few years of my life. With a home internet connection and a smartphone in my pocket, if my power goes out I can work away online for hours and hours. Power outages and network outages happen so infrequently that if we have reasonably good offline apps and Fat Caches, we're good to go. And not only that, but we're approaching a place where can continue working almost uninterrupted if both the main power and the network go down.
- brudgers 15y ago[From this post's great grandparent]"The apps should also live in the cloud and just appear on all the user's devices. In fact, the user's application "seesion" should be in the cloud too." If my session and my app are in the cloud and the cloud is unavailable, my session and app are not available. And what happens to my apps if I stop subscribing to the cloud for a few months? I still run Quickbooks 2004, ADT 2004, and VW 2008 for my business - will there be that kind of application persistence? [PS: I also use Sketchup 6 because of .dwg support and the ability to import into VW 2008] In other words, my business processes work, and moving crap to the cloud is an unnecessary expense. I don't need some jackass MBA deciding how I should work based on a survey of iPad users.
- joenathan 15y agoYou are missing the whole part about the "Fat Cache" - "A Fat Cache would retain all of its functionality and the user's most used data"
- untog 15y agoIt's extremely difficult to make that transparent, though. At some point, old data is going to have to be pushed out of that cache, and if you don't make it clear to users they're never going to know what they can and can't run.
- stcredzero 15y agoIt's extremely difficult to make that transparent, though. Actually, that transparency is exactly what will make or break this scheme. If know you can't make it transparent, then you shouldn't try. But the companies that succeed (probably Apple and Google) would make billions. At some point, old data is going to have to be pushed out of that cache, and if you don't make it clear to users they're never going to know what they can and can't run. That's why it's a >fat< cache, as opposed to a thin client. If you have a big enough cache, then it won't happen too often. It doesn't work absolutely all the time, but if it works almost all of the time, customers will be happy. And if it doesn't work, and your company also makes the hardware, then when the customer comes to the store, you tell them they need to buy a machine with more memory. Cha-ching.
- wmf 15y agoMS may be prepared to deliver something like that, since they have the old Danger/Kin stuff which was based on what you would call a fat cache architecture. MS also appears to be moving to a single-runtime (WinRT) future, so the "same" app may be available on phones, tablets, and desktops. The idea of migrating an app session between devices is going to be pretty difficult in most cases because people use different apps on different devices to access the same data; Twitter is an extreme example but there are plenty of others.
- stcredzero 15y agopeople use different apps on different devices to access the same data They do right now because they have to. Different apps/methods are best on different devices, and there's not enough thought to moving interfaces between devices. But if users didn't have to, and the mechanism worked well, they'd love it.