Live data from Hacker News

Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

nino.app

1–10 of 269 posts

Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#1
Nino is a radical approach to solve the app chaos problem for today's knowledge worker. I believe there are still too many tools; even using them becomes work in itself. I'm building all these apps from scratch in one place, using the same database and UI, with the flexibility to eventually support the majority of work from one "superapp."

Currently there are 18 apps (called "modules") on Nino:

- Database types: Sheet, Form, Calendar, Gallery, Board, Todo, List

- Composition types: Doc, Slide, Drive, Notebook, Canvas, Grid, Blog, Site

- Communication types: Channel, Chat, Meet

I want to improve these modules and build more. Your feedback is important!

FAQ: How is it different from Google Workspace, Microsoft 365, or startups like Notion and Clickup?

A: I think 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)

Let me expand on these points:

1. Consolidation

In Nino, pages and blocks are interoperable with each other. Google and Microsoft still have mostly isolated apps. Nino is one (super)app that supports 18 modules, saving you time from switching and integrating between different providers.

2. Offline mode

This is actually more complex than it seems, but I ultimately decided it's worth it, not only for people who need to work without internet, but also for everyone else who want instant page load. Everything is saved locally by default.

3. End-to-end encryption (E2EE)

This is just a preview and not open to public yet, but is something I have been building alongside since day 1. In fact, it's likely not architecturally possible for existing products to add later on. Nino is built to offer both E2EE and cloud features (backup, search, collaboration).

One more thing: pages on Nino are also publishable! There are blog and site modules, but you can also publish other modules (i.e. sheet, board, canvas, etc.) on your custom domain or on a free nino.page subdomain.

Give it a try and let me know how it can improve. I want to hear from you.

Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
nino.app

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#2
Congratulations on releasing your product! It looks super interesting. Some questions from the top of my head: - Where is the data stored geographically? (US, EU, or a specific country) - Do you plan on having multiple options for the web version (cloud vs self-hosted)

I find that data sovereignty is very important to me (it might not be for everyone), which is why I ask about those points specifically ;)

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#4
post #2

Congratulations on releasing your product! It looks super interesting. Some questions from the top of my head: - Where is the data stored geographically? (US, EU, or a specific country) - Do you plan on having multiple options for the web version (cloud vs self-hosted) I find that data sovereignty is very important to me (it might not be for everyone), which is why I ask about those points specifically ;)

Thanks! Data sovereignty is also top of my mind, but I think we should approach it not with the physical location of the servers/databases, but with the ability to encrypt, thus own, your data.

Currently it uses GCP with data centers in the US, but when E2EE is rolled out, I don't think it would matter where it's located? There might be legal complications so I'm also thinking of moving the physical databases to jurisdictions like Switzerland, if it comes to that.

Given the complexity of the backend, I think a self-hosted version might not be possible in the short term. However, single tenant versions (like GitLab dedicated) is definitely doable.

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#5
Security & privacy are tough selling points; fewer people care about either than you may think, and the existing platforms provide a lot more than most who do care are willing to admit.

Also the “too many tools” pitch sounds like an unhinged rant. There’s almost certainly a better way to phrase that, because otherwise the idea that the mere existence of a wide variety of tools bothers you doesn’t stand up to the “so don’t use them all” rebuttal. Maybe focus in the convenience factor, and the integration within your platform instead, as that is a genuine value-add.

Good luck!

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#6
Congrats for such an profound launch of kind an Army knife for office needs. I like this approach of "modules" very much, especially compared to MS365 cosmos where you've got the great four apps very prominent and new apps / functions hiding their potential power behind a lot of new names and rather confusing menues.

What is your vision about email? I know, it's not an advanced nor modern technology but still the established backbone of office communication, especially if you want to conquer the given field. Despite MS365 has Outlook as default app working with emails in other contexts is still a pain.

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#7
This is really cool -- congrats on the launch! The productivity worker's "app chaos problem" as you called it is a real problem and a solvable one.

I'm building something similar after spending 10+ years working with those numerous different apps day in and day out in quote-unquote "high stakes" white-collar roles. It's early days and I'm approaching it from a slightly different angle, but there's a certain amount of overlap between the two visions. I'm focusing on a smaller set of apps but more fleshed out set of features, aiming for feature parity with incumbents + my own features (which incidentally is why this is taking a while to build well...)

Curious to see how Nino progresses and we should connect later on when I have something tangible to show, if you're up for it

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#8
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.

Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

#10
post #2

Congratulations on releasing your product! It looks super interesting. Some questions from the top of my head: - Where is the data stored geographically? (US, EU, or a specific country) - Do you plan on having multiple options for the web version (cloud vs self-hosted) I find that data sovereignty is very important to me (it might not be for everyone), which is why I ask about those points specifically ;)

Thanks! Data sovereignty is also top of my mind, but I think we should approach it not with the physical location of the servers/databases, but with the ability to encrypt, thus own, your data. Currently it uses GCP with data centers in the US, but when E2EE is rolled out, I don't think it would matter where it's located? There might be legal complications so I'm also thinking of moving the physical databases to juri…

Unfortunately, it always matters. There's always someone who wants to know where the data is physically located and they will always want an answer for it.
Post reply on HN