Super impressive app by the look of things, but as you asked for feedback, it is (to me) very confusing on the product side of things (i.e. what is it and why does it matter to me).
As a business user it's not clear how I would use it, and why I would care.
Your front page reads as:
> Nino is a collection of apps that can interoperate with each other on the block-level from one uniform interface. It has interoperable pages and blocks. It is flexible, extensible, and adapting to your needs as you grow, as Nino helps you consolidate tools and reduce costs. It has page sourcing so you can view pages in a different way. It has page embed, so you can sync page to another page. It has sync block to another page, but you can also block mirror and sync block on the same page.
A good comparison against your front page would be against monday.com or Asana who start with use-cases and practical application. See Monday:
> Monday - A platform built for a
new way of working. What would you like to manage?
> * Work Management - Run all aspects of work
> * Sales CRM - Streamline sales processes
> * Dev - Manage product lifecycles
Then if I click any of those categories, it goes into the exact ways it can help me.
+1 to this. Focusing on usecases would be great. ex: I wanted to see what features were available for your sheets module.
Was willing to spend 5 minutes on a walk. Tried the web app - ios safari is not supported :( downloaded the ios app and registered. Got a totally blank app - no onboarding, no template / samples, no obvious way to import from my existing google sheets to see how things scaled. I added a datasource and a few fields (which felt confusing) and my walk was over.
Google Chrome can't even use it's rendering engine on iOS, you're comparing WebView implimentations (which Apple will always be superior at... since they control the OS and every API entitlement).
I totally agree. Coming across Simon Sinek's 'Start with Why' has helped me a great deal in communicating in general. Even in conversations this applies:
In terms of this theory you should communicate like this: Why, How, What
You are starting from your 'What'.
I haven't really grasped the core of your product, but to restructure it could be something like:
Stop wasting time looking up documents, e-mails and chats in different systems. Stop paying for 20 different single purpose services just to run your business.
By having everything in one place it is easier to find and share information throughout you business. Creating custom combinations of docs, chats, sheets, forms, etc will allow you to create the tool to support your own processes and ways of thinking rather than having to learn some app's way of thinking.
Nino allows you to quickly build your own custom flows using modular building blocks. Create the tools that you need and have all of your information in one place.
> interoperate with each other on the block-level from one uniform interface
Sounds quite a bit like Notion. A comparison would be apt.
Also sounds a bit like OLE / OpenDoc on desktop, embedding an Excel sheet into a Word doc along with an Access form. If it can do that, it could make quite a demo.
> very confusing on the product side of things (i.e. what is it and why does it matter to me)
My initial thought was, this vision looks like what happens when a company realizes that their core product is less valuable than everything adjacent to it and starts growing their product a dozen different directions simultaneously.
But maybe there's something different about embracing this holistic vision from the start, as opposed to trying to be focused and then getting forced into scope creep.
As a business user it's not clear how I would use it, and why I would care.
Your front page reads as:
> Nino is a collection of apps that can interoperate with each other on the block-level from one uniform interface. It has interoperable pages and blocks. It is flexible, extensible, and adapting to your needs as you grow, as Nino helps you consolidate tools and reduce costs. It has page sourcing so you can view pages in a different way. It has page embed, so you can sync page to another page. It has sync block to another page, but you can also block mirror and sync block on the same page.
A good comparison against your front page would be against monday.com or Asana who start with use-cases and practical application. See Monday:
> Monday - A platform built for a new way of working. What would you like to manage?
> * Work Management - Run all aspects of work
> * Sales CRM - Streamline sales processes
> * Dev - Manage product lifecycles
Then if I click any of those categories, it goes into the exact ways it can help me.