I'm using whatboard.app to do much of this now, but your solution has a desktop app which is a nice addition.
Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
111–120 of 269 posts
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#112Is this related to Zoho? I ask because many screenshots have the same Zoho colors and logos.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#113One of the most important features to get right for tools like this is collaborative editing. It's incredibly difficult to get this right (live preview, conflict resolution, history management, etc), especially given how the vast majority of users are non-technical folks (which aren't used to toolks like git). Could you expand a bit on how you intend to tackle this problem in Nino?
I actually think this hyper-granular realtime collaboration like in Google docs is slightly overrated. I think it’s ok to have more a git-like workflow where feedback and changes happen over cycles. As a programmer, I don’t give a shit about your working directory. I do care, however, about your commits :) All I’m saying is this CRDT craze isn’t always necessary or even appropriate for many products. It adds a lot of…
I agree. I haven’t yet interviewed a user that views realtime collaboration as something desirable in itself. In my research, user mostly are forced to do this kind of collab because it’s still better than coordinating via side channels such as email or phone. It has lower friction but at a very high usability cost. In contrast it makes people undervalue the importance of a structured plan of execution for projects with a significant number of collaborators. There are practically no polished, in-between, git-like experience in mainstream tools. The outcome of real-time for users is always remembered as messy and frustrating. I don’t even agree with the premise of shared control as being an effective basis for creative or productive process at large, it is useful for brainstorming and exploration in some specific cases, or highly specialized and niche settings like pair programming. IMHO this is super valued by developers and marketers because it’s challenging, cool and it makes for a good pitch. Not rare to see people who conflate digital collaboration with shared control, thinking they’re synonymous – such is the influence of these modern workflows. We can never know how good other collaboration strategies can be if alternative experiences are under-developed and people default to shared control.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#114Super 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…
> 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.
Microsoft was pushing something like that few years ago under the name Fluid Framework: https://youtu.be/tPw5kFkXtt4
But seems to have devolved into generic state synchronization library these days.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#115Super 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…
> 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.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#116Wow, I have never been more impressed with any other Show HN before. The sheer number of features and platforms you have covered and also keeping to some core engineering principles at the same time is extremely impressive. I will be trying this product for sure and wish you all the best with this app.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#117To add to what other commenters said: Your app sounds very interesting, but the use cases and use scenarios remain a bit unclear. Personally, I would love to be able to just try it without having to sign up. Right now, the copy leaves the user experience very much in the dark
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#118This looks really cool! I tried to sign up but it doesn't seem to be sending out verification emails right now. Will give it another go a bit later
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#119Is this done by a single dev? If so, that's a massive risk for anyone who might start using these tools.
Re: Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)
#120One of the most important features to get right for tools like this is collaborative editing. It's incredibly difficult to get this right (live preview, conflict resolution, history management, etc), especially given how the vast majority of users are non-technical folks (which aren't used to toolks like git). Could you expand a bit on how you intend to tackle this problem in Nino?
I actually think this hyper-granular realtime collaboration like in Google docs is slightly overrated. I think it’s ok to have more a git-like workflow where feedback and changes happen over cycles. As a programmer, I don’t give a shit about your working directory. I do care, however, about your commits :) All I’m saying is this CRDT craze isn’t always necessary or even appropriate for many products. It adds a lot of…
> I actually think this hyper-granular realtime collaboration like in Google docs is slightly overrated.
I have to disagree. It's absolutely necessary for a lot of workflows, especially when people are collaborating on a doc in real time during a meeting (super super common), or when you've got 10 reviewers of a doc all leaving their feedback in comments, and comments responding to comments, over the course of the same hour.
The model of clean commits works well for code. It doesn't work well at all for business team documents that are in-progress.