• 1 Post
  • 77 Comments
Joined 2 years ago
cake
Cake day: June 28th, 2023

help-circle









  • peak of UX

    Good UX.

    give an example

    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.


  • 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.

    people dont get familiar with UX

    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.

    ticketing system

    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

    using email for business process must die

    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.


  • Your claim with the api is outright wrong. The difference is between client side and service only api the rest is hyperbole. That gap is MASSIVE functionally. Client api is responsive, fast, access to local OS and local hardware. Service side has its place, but its service limited only. Severely limits access to other services which is very important when moving data.

    You have conflated User Experience with User Interface. I didnt say UI for that obvious reason. The experience matters a lot. Having to open and process the same flow of task from one app to another app breaking concentration is bad fucking UX. Losing context is bad UX the list goes on. it reduces accuracy, & performance and ultimately productivity. Something as simple as classing becomes simple when the context of the conversation is very easy to get and more accurate when you dont duplicate an entire chain.


  • Highly doubt it, maybe a small organisation which would make sense by your comments.

    Outlooks feature list is huuge. Large list of functions in Calendering alone is unmatched.

    most of these things are dying out.

    Bollocks.

    The API is the backbone for large organisations that extends that large amount of Outlook functions beyond 365 limited services. That is being cut off in an anticompetitive move by Microsoft. It allows for information management and automation to be verified by people with simplicity and a familiar UX.




  • An Outlook replacement. The new web Outlook is absolute garbage with zero addin api like the old one had

    Make a replacement Outlook that connect to imap service or something that’s close to feature matching (calendaring ect) and its game over for two huge revenue streams. it’s a cornerstone of Enterprise 365 and they refuse to listen to clients.

    Everything else is “good enough” in FOSS but nothing gets close to Outlook functionally.