To not much official fanfare on Thursday, the Windows operating system turned 40 years old, marking four decades since Windows 1.0 debuted in the United States on November 20, 1985. Its midlife milestone comes with a crisis, though. Diehard Windows users are switching to Linux for a variety of reasons.
For one, gaming is finally better on Linux machines, which makes the moat Windows dug for itself a little more passable. Add to that the end of support for Windows 10 in October, the growing frustration among power users about Microsoft Recall, and the growing number of polarizing features, and power users are finding plenty of reasons to make the switch to Linux.
It’s unclear if the wave of Windows power users loudly moving to Linux has crested yet, or if this is just the beginning. That said, the past year has seen a flood of articles like this one, scores of posts on Reddit, and YouTube videos documenting and occasionally evangelizing the conversion to Linux.
If it’s done right. So, just like an app.
I’m already speaking for switching from Outlook with API to apps, you don’t need to sell it to me!
Read this again.
You’re advocating for moving data via Outlook. Mate, I hate to break it to you, but this is peak insanity!
UI is integral to US. That’s why I mentioned it.
Also: “familiar UX” makes little sense. People don’t get “familiar” with UX, the UX is either good or bad. That’s why I mentioned both.
Here’s the thing: it shouldn’t be “teh same flow of task from one app to another”. Modern apps tend to encompass the entirety of a process.
That’s what ticketing systems are for.
In general: using email for business processes must die just as much as using Excel for a “database”.
So you’re advocating for slowing process, bad user experience, and duplicating shitty email functionality in every app to receive and send email limiting communications. Got it.
Yes they do. Duplicating email into other systems that doesnt have anywhere near the same functionality and flow as their dedicated email app which is designed for email is frustrating, and restricts communication.
Wtf does classing have to do with ticketing systems. It applies to records management, project management, legal case management, the list goes on. It applies to most business
Oh my sweet summer child. I’ve got news for you: email is HOW business is conducted. That is not going away any time soon.
Yeah, if you ignore everything I said and invent your own stuff, then this is exactly right.
I’m still trying to wrap my head around the fact that you think that email is somehow the peak of UX.
Could you give me an example of a process that’s much better handled via API to Outlook than literally anything else?
Wow, these all sound like important things that should definitely not be handled via Outlook. But, again, I might be super wrong - please give me an example, because maybe we’re talking about two different things.
Are you from the US?
Good UX.
Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business. To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services.
Just to be clear I am not advocating for building Microsoft Lotus notes (Teams), not at all. Quite the opposite.
However jumping between apps is how mistakes are made, and evidence lost from laziness or “too busy”. IMO Email communications should only be handled by Outlook or a dedicated email client that has the depth of functionality for good communication. Addins provide the middleware between different products and services to integrate them. It can even be completely transparent to the user.
Bringing this back to the topic. The shift to the web only Outlook means no more BYO libraries, no more .net , no more OS api, no more COM api. These provide an enormous amount of capability for addins to leverage and provide integration. Now with website Outlook, the api is incredibly limitted and entirely controlled by Microsoft, there is no BYO libraries and connectivity and those existing web api’s can and are removed at whim removing the ability to conduct business on 365.
So if someone can build an app like Outlook that has rich email, calendaring and pure depth of functionality that it has. This would be a massive barrier removal if not in my oppinion the last barrier for mass business FOSS adoption.
This is not an example. What type of communication? Are you classing emails? Are you classing internal documents? Are you classing marketing material? Are you classing internal comms?
This description screams “use a proper ticketing system” to me but, again, I feel like I don’t have enough information about the process you’re talking about.
A badly designed process or the wrong app.
Again, this all sounds like you guys are using the wrong tools for the job, but would need to hear more details.