251 karma · joined October 14, 2019
Thanks guys for the feedback. I think it's pretty clear what should be worked on next.
As for the switching to mobile scenario, it also makes sense. I'll think about this, it might be a button that allows you to "force sync" everything.
Thanks for the detailed explanations :)
Editor.js looks interesting. Nino Doc is based on ProseMirror. Never heard of grist before but I think react-datasheet-grid is a pretty good. I've been itching for a frontend rewrite of Nino Sheet.
Could you share your use case on embedding a single record? I disabled that for now because I imagined people would usually embed all records together in a certain view.
Hm I'll think about searching for blocks in autocomplete, or perhaps some way to use advanced search inline.
Your experience in offline mode was actually expected. I assume you never opened the other pages on your phone, so they weren't saved on your device. Nino's not syncing all pages all the time, but only the ones you open, for performance reasons. Do you think having some sort of mechanism to pre-sync certain pages is necessary?
Thanks for the actionable feedback regarding marketing and onboarding. You're spot on that the home page is being like docs for other engineers, I didn't even realize I was doing that.
1. Nino competes with a better foundation and architecture. It is true MSFT and GOOGL have more engineers, but I'd say startups don't compete with thousands of them, just a dozen or fewer actually working on the product. Btw, pivot tables are supported, check out the "Widgets" button at top right corner.
2. You have good points here. The communication on the use cases can definitely be improved. As you and others have pointed out, Nino's landing page does feel like a documentation page for other devs right now...
3. It is solo and I view it as a life's work in progress. It is precisely because I want it to stay for the long term that I've resisted seeking any VC for now, to not dilute and lose too much control in the beginning.
Thanks for the recommendation on the possible directions going forward, I'll think about them!
Interesting that you mentioned fine-grained security. Currently block-level access control can be achieved with block embeds, but it has to be done one by one. I looked into enforcing access based on a query for page embeds (so allowing only portions of the page), it turned out to be non-trivial! Might try to implement in the future.
Thanks for breaking down the different levels of self-hosting. I'll keep them in mind.
You mentioned you were in a similar place to this, I'm curious to hear about your experience and the specific decisions you made back then, if you're comfortable sharing.
Self-hosting might be too complex to setup, but do you think single tenant offering helps? I don't know if it makes sense for individuals tho.
In addition to HTML & CSV, there is an option to export JSON, which supports more formats. In a way, it is an open format (.json) but I'll have to add relevant documentation. PDF support will also come at one point.
For the Sheet module, when you create a new field in the modal view, it'll be available to all other records too within the page, as you probably found out.
Side note: I did start implementing PDF exports, but for anyone curious, it's actually a lot more complex than imagined. There is no easy way to turn HTML to PDF (if anyone knows otherwise, please share) and there are font and language complications.