AsyncGo VS Nodewood

Hey everyone! I've been working on an async collaboration app for some time (https://asyncgo.com) and through talking to customers we've been refining the idea further and further, and are now focused on helping teams discuss and make improvements to how they work. It's something a lot of teams are struggling with as they moved to remote, then hybrid, and in general are doing a lot of iteration around improving... - Source: Hacker News / about 2 years ago

I am building AsyncGo (https://asyncgo.com) which is still evolving but it is a kind of forum for businesses structured around having important conversations and documenting the decisions that come out of them. I built it to have something simple and lightweight for discussions for remote teams, as an alternative to meetings and using more heavyweight methods like issues for conversations. It is still early days... - Source: Hacker News / almost 3 years ago

I've built a web app at https://asyncgo.com that's all about helping your team collaborate better. It's designed for remote work, but can really help any team. The idea is that we can help you move many (or even all) of your meetings and chat conversations to our app, where they are structured better and are easier to use as well as reference later. Source: about 3 years ago

I built https://asyncgo.com, it's built for teams but you could use it by yourself. Source: about 3 years ago

Hey, thanks for the mention! I'm the creator of Nodewood, and I'm happy to answer any questions anyone has on it, or really anything else in the space I can help with. Source: about 1 year ago

This is largely why I built Nodewood [1]. Every time I wanted to start a new project, almost always a SaaS idea, I'd skip over the "boring stuff" like building user management, subscription management, teams, admin, all that, to get to the meat of the business logic, to make sure I had a valid idea. But I still needed all that stuff eventually, so I'd have to lose time later building it all in! So I decided to... - Source: Hacker News / almost 2 years ago

This is actually part of why I created Nodewood [1], because every new Node project required pulling all that together, and every new SaaS idea I had had the same basic requirements (user management, subscription management, teams support, etc). Then I figured, if I found this useful, surely others would too, so I packaged it up and have had a few happy customers since then, who have helped me refine it, which... - Source: Hacker News / almost 2 years ago

Well, I've spoken about this before, and on here no less, but only really in response to posts like this. I don't do any advertising or speak about mine except in interviews, since it's usually indicative of the kind of requirements they're looking for. I created a SaaS bootstrap for Javascript called Nodewood [1]. It actually started as just a template for me, because there's a lot of setup for each new JS web... - Source: Hacker News / almost 2 years ago

Disclaimer: I'm the author of the following boilerplate. Nodewood (https://nodewood.com/) is a Javascript SaaS boilerplate built to take advantage of using Javascript on the server and in the UI. Models, Validators, and other business logic can be re-used in both builds, so you don't have to write, rewrite, and maintain that logic in both places, or in different languages. It has built-in subscription management... - Source: Hacker News / about 2 years ago