21–30 of 165 posts
This looks like the exact opposite of what I would do if I were to redesign operating systems. The job of operating system is just to run application and get out of the way, and most importantly be deterministic and reliable. I don't need my OS to "predict what I might need", I know what I need myself.
Please tell me why my workflow, which works for me, sucks more. What is this magical 'friction'?
Reads like it was written by an MBA.
Oh boy I’d like to play with something new and exciting like this and was sad to hear it’s just a design mock-up/idea. The OS space seems to have been quite stale for a decade or two, is there anything super exciting and different out there from a UX perspective? Remember installing Linux in the late 90s or rooting Windows phones and installing whatever latest Android OS was available in the early days of iOS and And…
Have you looked into Sailfish? https://sailfishos.org/ I'm not affiliated (nor have I actually used it) but it looks like an interesting alternative approach to phone UX, and one that you can actually use! I'd be interested to hear any stories HNers have with it.
> The process of moving from App to App generates friction that takes you out of flow and distracts you from your intentions. Please tell me why my workflow, which works for me, sucks more. What is this magical 'friction'? Reads like it was written by an MBA.
In gmail, you have a shipping confirmation, a calendar invite, and a team newsletter.
In slack you have a question from a customer, a review request from the team, and a poll for the next offsite.
And in Docs, you have a new project summary, a budget proposal, and a post-mortem doc.
You see, how you actually have 9 different things to do (intentions), but the number of apps you have is just 3? Sometimes, you'll have a thread of things across multiple apps. So despite switching "apps" there's still mental overhead of piecing things together. It's easy to overlook, but sometimes switching apps can causes an effect like walking into a new room, and forgetting why you were there in the first place. Hurting your focus/flow.
This looks like the exact opposite of what I would do if I were to redesign operating systems. The job of operating system is just to run application and get out of the way, and most importantly be deterministic and reliable. I don't need my OS to "predict what I might need", I know what I need myself.
> The process of moving from App to App generates friction that takes you out of flow and distracts you from your intentions. Please tell me why my workflow, which works for me, sucks more. What is this magical 'friction'? Reads like it was written by an MBA.
Okay, consider you have 3 apps: gmail, slack and google docs In gmail, you have a shipping confirmation, a calendar invite, and a team newsletter. In slack you have a question from a customer, a review request from the team, and a poll for the next offsite. And in Docs, you have a new project summary, a budget proposal, and a post-mortem doc. You see, how you actually have 9 different things to do (intentions), but t…
Also OS doesn't fix any of that, especially for the webapps as they tend to not integrate well with anything else
Just for context: this is a 4 yo design study by friend and amazing product designer Jason Yuan, who also worked on Sprout.place and more recently some stuff at Apple (@jasonyuandesign). A lot of the comments currently seem to miss this and are focusing on immediate feasibility, “successful” design, or ability to deploy irl. That is not the point here. Things like this are both creative exposition, as well as corner…
That said, it's absolutely valid to question stuff like this. A lot of design student type stuff miss HUGE usability issues.
Just for context: this is a 4 yo design study by friend and amazing product designer Jason Yuan, who also worked on Sprout.place and more recently some stuff at Apple (@jasonyuandesign). A lot of the comments currently seem to miss this and are focusing on immediate feasibility, “successful” design, or ability to deploy irl. That is not the point here. Things like this are both creative exposition, as well as corner…
I get a lot of value from HN, but technocratic communities often fail to understand the value of reimagining everyday things.
They sometimes get so caught up in the technical bits and pieces they don't like about something you end up with responses like those you in this discussion, or HN's reaction to Dropbox, or Shallots Slashdot's reaction to the iPod.
Just for context: this is a 4 yo design study by friend and amazing product designer Jason Yuan, who also worked on Sprout.place and more recently some stuff at Apple (@jasonyuandesign). A lot of the comments currently seem to miss this and are focusing on immediate feasibility, “successful” design, or ability to deploy irl. That is not the point here. Things like this are both creative exposition, as well as corner…
Has anyone attempted to implement this into an existing Linux DE? Or a full screen web app experience?