The only real issue with it is that the current generation of their smartphones doesn't come with enough memory. Only 8GB (S22) or even 6 (S21FE). You need more for decent multitasking.
But I think generally it's pretty underrated. It had done really annoying issues in the beginning but right now I could imagine doing a working day on it. I don't because I am really a power user, but for someone with normal office use I could see it being viable.
I wish this feature would make it to mainstream AOSP because right now it's too obscure to really take off. They made a developer thing with Android 10 but didn't take it the whole way after that.
Since we're fantasising about future computers I hope there won't be more than 8Gb necessary to multitask. I remember running Windows and Office in the 90s on 16Mb. Seems like the 1000-fold increase in memory was mostly negated by wasteful software engineering...
I don't doubt some things swap (pagefile, windows after all), but whatever its putting in swap is not noticeable. I don't experience stalls.
My main issue with Dex is the perennity of the system. Is Samsung going to keep pushing this, or will a native android version takeover? Or maybe at some point they'll say "well that didn't work out" and abandon it completely?
I want to believe!
Every year I get closer to being able to do my work completely off a phone. I also think 8GB of RAM is plenty. Most administrative tasks can be done on that, and for the heavy tasks, you could always leverage a remote server. Think of github codespaces, or modern virtual machines in the cloud. Sure, you need internet, but don't you always, for this kind of workload?
Yeah, yeah, I want to believe :)
Agreed, this is also a worry of mine. In fact they did exactly this with Linux on DeX.
> Every year I get closer to being able to do my work completely off a phone. I also think 8GB of RAM is plenty.
Remember that Android devices don't do swap. What I see with DeX is a LOT of tab refreshing when it starts running out of memory. Which is really annoying when you're trying to do actual work (e.g. going to an Excel sheet to look up something, but then going back to the browser to continue filling in a form, but in the mean time this has reset due to a forced page reload).
Right now I'm using termux, which is working really really well. I'm amazed! I have this big PHP app wich runs perfectly fine on it, with dependencies and all, I honestly expected trouble, but it just worked.
As for the swap: yeah that sounds annoying :(
Unfortunately the restrictions in later Android versions make it more and more difficult for Fredrick to continue supporting it. I'm currently using the F-Droid version which targets an older Android version but eventually that will become impossible too because newer android versions will eventually drop the older APIs altogether.
In particular in later Android API versions it's no longer allowed for an APK to load binaries from other sources and execute them there. Which makes the apt repository impossible. So what should it do? Include all binaries in the APK? Or distributute each app inside termux as a separate APK? Neither option sounds very appealing.
You also don't use e.g. the same pair of pants for swimming and office work.
Mobile OS's give you almost no control over anything, but you're forced without choice to use them and their apps you have zero say over for half the things today (e.g. parking, banking, choosing the color of your LED lamp, ...). It's great to keep that separate from my desktop computing workflow.
Unless I can bring my home computer paradigm to the phone. But are those parkings, banks and LED lamp manufacturers going to allow me to run their stuff on my OS of my choosing over which I have full control?
But as far as document storage, Maybe the dock acts as a home server? Either way, it seems like off-device document storage is a problem that's been solved multiple ways already?
My phone can only run some stupid games and some web apps. You cannot program on it and you have a very limited choice on what you can run on it.
1) One device that does everything will work well if it does everything well. I can take a laptop anywhere and have a usable computer just about everywhere. A phone dock works in locations where you visit often and have a dock, and I wouldn't trust docks in locations I don't control. If I want to work at a coffee store or in a car I can't use a dock.
2) Human design needs to be centered around humans. Humans are designed to rapidly take in lots of information through vision. Designing a device that removes the primary interface between human senses and the device is making that device significantly less useful. I would guess that 90% of the time I spend on my phone is spent reading. I don't want to be read to, but I already have that option if I want. Purposely ruining the device UI and its primary purpose in an attempt to reduce "phone staring" is directly hostile to users. Any sort of general computing device should have the ability to engage directly with your most detailed and useful sense.
Like, with TVs. Like a lot of people I want something more like a display, than a crappy computer running a crappy operating systems, since I use my own set-top box and such. But I don't think the parts needed to turn a TV into a crappy Android computer are really all that expensive. (Also "thin clients" are often just decent computers themselves!)
All that being said I personally like the idea of having a giant house supercomputer like the one in Enterprise, with various tablets and such just interfaces to that one single computer.
have you heard of Google Assistant? It does exactly what you are saying. They do have a screenless device too. Also there is Amazon Alexa that basically does the same thing.
I'd like to be able to get information, store information, get and receive calls, texts, slack messages, make appointments, etc. I started with "what do I want to be able to do on a regular basis, from anywhere I am?" Then I go to "does a technology exist which allows me to do that without a screen?" Google Assistant is close-ish, but there's still a lot of work to be done to get past "the Beat up Martin -> Eat up Martha problem," and TBH I don't think they're putting much work into it anymore, progress seems stalled.
The article's author. I agree with the every single point of the article and I want to develop author's idea here because it resonates with some ideas of mine.
> I'd like to be able to get information, store information, get and receive calls, texts, slack messages, make appointments, etc.
This is what Iphone does maybe in the best possible way. My needs are: to write, to program, to use Vim and Emacs, to be as close to body as possible, to be able to control others computers and screens in my house.
> the Beat up Martin -> Eat up Martha problem
That's why author's poind about keyboard-centric device is timeless.
But Google was never close to the computer the author describes (in my opinion). Perfect listening (recognizing everything with no errors) is not a big deal if you already have a perfect keyboard but perfect sounding of anything happening on the screen is where the progress is absent.
Imagine working with CLI using sound only in such a way which make your CLI experience better than GUI.
> for some of these tasks you don't need wifi connection on
And all of this abilities are literally baked in chip. For example, if Google (or user/owner of the device) decides to change "OK Google" to "OK Alphabet" than all the old chips will be unable to support such a newcoming. So, I do not agree that the technology exists, these are way closer to speaking dolls than to computers.
Its not baked into chip, its software and gets updated just like your phone or computer when its connected to the internet.
> We need to develop a voice assistant technology which retains context and can "understand" in a more conversational style
Former is about output device while latter is about input one. What is the connection?
1. I don't think we need a phone and a home computer. There's really very little reason at this point why they can't be one and the same. A device that plugs into a dock at home and becomes a home computer, and when you undock it it becomes a phone. And I don't mean the ham-handed attempts we've seen, I mean a full-on contextual OS switch.
2. I think the next major evolution in phones should be removing the screen. We need to develop a voice assistant technology which retains context and can "understand" in a more conversational style, but I think that once we've jumped that hurdle there would be plenty of people—for whom phone-staring is currently an act of boredom or filling time—who would willingly get rid of that screen in favor of a voice assistant.