>Nino is a radical approach to solve the app chaos problem for today's knowledge worker ... I'm building all these apps from scratch in one place, using the same database and UI, with the flexibility to support the majority of work from one "superapp eventually."
Maybe I can see some use-case for personal use (big maybe), but right off the bat, you can't use this at any company (small startup or enterprise), for several reasons: Lack of functionality, lack of organization-based group and access control workflows, auditing, user provisioning/de-provisioning, lack of cross-organization document sharing and collaboration and compatibility, plugin support, email integration, domain hosting, etc. etc.
I'm not even sure a motivated individual contractor could use this professionally due to the need to collaborate with their customers. I'm not even sure you could dog-food this while managing Nino Inc.
>Nino is one (super)app that supports 18 modules, saving you time from switching and integrating between different providers.
Is that even a real problem?
Most places will use either Microsoft 365 or Google Workspace - those platforms are very well integrated internally. MS365 has all the apps you built except they are feature-rich and some are industry standards (like the Office suite), plus much more - and everything is very well integrated.
But that isn't enough. Sometimes users may prefer, for example, Confluence as a wiki instead of the MS365 Sharepoint wiki - the reason why is because they want to choose a 'best of breed' solution for their use case .. or it may just be a subjective preference. In that case, yes, the integration isn't as great but it is workable (there are plugins to allow deeper integration of external applications). Your solution won't be able to get away from that either. Even if I like your Todo and Notebook apps, I may prefer using Zoom for conference calls and Slack for chat .. what happens then?
A lot of features you mentioned are actually implemented (role-based permission, cross workspace sharing, domain hosting...) and some that will come (audit logs and other enterprise things).
I get the best-of-breed argument. Nino's thesis is that people will find more value if enough tools are bundled in one place.
No, they aren't. I'm not trying to be argumentative, but there is a difference between true support and a superficial check-mark.
>I get the best-of-breed argument. Nino's thesis is that people will find more value if enough tools are bundled in one place
I'd like to interrogate this a little more. Why would someone not go with MS365 or Workspace?
I can see your answer of:
>Nino has a better foundation to (1) consolidate a lot more apps than they currently do, (2) drastically improve speed with offline architecture, and (3) offer unmatched privacy and security with end-to-end encryption (coming soon)
Taking this point by point:
1) Your ambition is to have more apps, but the reality is that TODAY, both MS365 and Workspace actually have MORE applications integrated, and those applications are much more feature-rich.
2) MS365 certainly has deep offline integration. Workspace, I'm not sure what their capabilities are.
3) Neither MS365 nor Workspace supports true e2e (though I seem to remember Workspace having some option to import your own keys for client-side encryption) - regardless, I'm not sure that's enough as a selling point. Also, e2e has many challenges around the UX of key management, rotation and sharing.
By the way, MS365 and Workspace are not the only games in town. If you want to see another example of a 'super-app' that supports a million 'modules' take a look at ZohoOne - they support everything under the sun for a relatively low price, and all of it is mediocre (at best).
---
Another thing I can't gauge from your page is, what it means for one of your modules to be very well integrated against another. You have a chat app and a slide app .. how do those work together that puts MS365 to shame?
Maybe I can see some use-case for personal use (big maybe), but right off the bat, you can't use this at any company (small startup or enterprise), for several reasons: Lack of functionality, lack of organization-based group and access control workflows, auditing, user provisioning/de-provisioning, lack of cross-organization document sharing and collaboration and compatibility, plugin support, email integration, domain hosting, etc. etc.
I'm not even sure a motivated individual contractor could use this professionally due to the need to collaborate with their customers. I'm not even sure you could dog-food this while managing Nino Inc.
>Nino is one (super)app that supports 18 modules, saving you time from switching and integrating between different providers.
Is that even a real problem?
Most places will use either Microsoft 365 or Google Workspace - those platforms are very well integrated internally. MS365 has all the apps you built except they are feature-rich and some are industry standards (like the Office suite), plus much more - and everything is very well integrated.
But that isn't enough. Sometimes users may prefer, for example, Confluence as a wiki instead of the MS365 Sharepoint wiki - the reason why is because they want to choose a 'best of breed' solution for their use case .. or it may just be a subjective preference. In that case, yes, the integration isn't as great but it is workable (there are plugins to allow deeper integration of external applications). Your solution won't be able to get away from that either. Even if I like your Todo and Notebook apps, I may prefer using Zoom for conference calls and Slack for chat .. what happens then?