this post was submitted on 24 Nov 2025
233 points (98.7% liked)
Linux
10299 readers
682 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.