What will UX look like with the current SaaS & micro-SaaS Cambrian explosion?
Doฤa Armangil
3 replies
The average employee was using 11 applications even before the micro-SaaS phenomenon.
Nowadays SaaS vendors are offering an ever-growing number of ever more specialised applications.
๐ง๐ต๐ฒ ๐พ๐๐ฒ๐๐๐ถ๐ผ๐ป ๐ถ๐ ๐๐ต๐ถ๐:
Would employees be content with juggling between too many applications, or would they prefer using only one application that fits their role and their line of work?
Replies
Nitesh Jamod@nitesh_jamod
With the SaaS and micro-SaaS explosion, UX will focus on hyper-specialisation, simplicity, and seamless integrations, prioritising personalised, intuitive experiences that cater to specific user needs while maintaining scalability and flexibility.
Share
@nitesh_jamod I agree with you that UX will/should focus on seamless integrations, but which integration technology will enable seamless UX?
To me a core feature is ๐ฐ๐ผ๐บ๐ฝ๐ผ๐๐ฎ๐ฏ๐ถ๐น๐ถ๐๐, and by that I mean a SaaS application must be able to call another SaaS application which must be able call another SaaS application etc.
So let's look at how composable the current integration technologies are:
* ๐ฅ๐๐ฆ๐ง, ๐๐ฟ๐ฎ๐ฝ๐ต๐ค๐, ๐๐ฆ๐ข๐ก-๐ฅ๐ฃ๐ ๐ฎ๐ป๐ฑ ๐ผ๐๐ต๐ฒ๐ฟ ๐๐ฒ๐ฏ ๐๐ฃ๐ ๐๐ฒ๐ฐ๐ต๐ป๐ผ๐น๐ผ๐ด๐ถ๐ฒ๐ ๐ฎ๐ฟ๐ฒ ๐ป๐ผ๐ ๐ฐ๐ผ๐บ๐ฝ๐ผ๐๐ฎ๐ฏ๐น๐ฒ. Why? Because when a REST API calls another REST API behind the scenes, then how do you authenticate the end-user? Also, composing these APIs brings with it the risk of network timeouts, because you never know how long an API call will take. I was even able to obtain a software patent from the USPTO on that last point.
* ๐ ๐ถ๐ฐ๐ฟ๐ผ-๐ณ๐ฟ๐ผ๐ป๐๐ฒ๐ป๐ฑ๐ ๐ต๐ฎ๐๐ฒ ๐๐ฒ๐ฟ๐ ๐น๐ถ๐บ๐ถ๐๐ฒ๐ฑ ๐ฐ๐ผ๐บ๐ฝ๐ผ๐๐ฎ๐ฏ๐ถ๐น๐ถ๐๐. Micro-frontends typically cannot be nested beyond 0-2 levels at most, because the screen real estate that is allocated to each micro-frontend diminishes significantly with each nesting level.
* ๐ง๐ต๐ฒ ๐ ๐๐๐ ๐๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฒ ๐ถ๐ ๐ป๐ผ๐ ๐ฐ๐ผ๐บ๐ฝ๐ผ๐๐ฎ๐ฏ๐น๐ฒ. In this architecture that is used for consumer applications, there is only one web frontend (typically a single-page application) and many SaaS/API backends, and all integration happens through the frontend. This means that a SaaS or API cannot decide by itself to call another SaaS or API, it must wait for the frontend to approve and implement the integration on its behalf.
To my knowledge ๐ค๐๐ผ๐ฟ๐๐บ ๐ถ๐ ๐๐ต๐ฒ ๐ผ๐ป๐น๐ ๐ถ๐ป๐๐ฒ๐ด๐ฟ๐ฎ๐๐ถ๐ผ๐ป ๐๐ฒ๐ฐ๐ต๐ป๐ผ๐น๐ผ๐ด๐ ๐๐ต๐ฎ๐ ๐ผ๐ณ๐ณ๐ฒ๐ฟ๐ ๐ณ๐๐น๐น ๐ฐ๐ผ๐บ๐ฝ๐ผ๐๐ฎ๐ฏ๐ถ๐น๐ถ๐๐, and this makes Qworum a technology supplier to consider when developing any sort of web application. Do be aware though that Qworum requires a browser extension to be installed, and that's why I am currently targeting the business applications space.
Feel free to give Qworum a whirl, local development is free, and for this Product Hunt launch I am offering 3 months free on the paid subscription.
@doga_armangil Great insights! I completely agree that composability is key for seamless UX in SaaS applications. It's interesting how Qworum addresses the limitations of traditional integration technologies, especially around nested API calls and authentication. I'll definitely explore how Qworum can enhance composability in web applications!