Live data from Hacker News

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

nino.app

231–240 of 269 posts

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

#232
post #157

If you're going to offer an offline-capable Linux app then no-one wants to use Snap. AppImage or Flatpak is the way.

Curious what the argument is against Snap? They allow very easy updates

It doesn't work on various distributions, lots of people disable it because of various issues like it being much slower to start, it can only connect to one backend at a time (which is Canonical's proprietary one) unlike Flatpak, and generally the Linux community has settled on Flatpak and AppImage as the preferred universal packaging formats.

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

#234

Any chance you can add a link to download for Windows but NOT on MS Store? I (and perhaps many others) have the bridges to the mothership torn down, so not MS Store.

Can you elaborate? Are you not able to access MS store for some reason?

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

#235
post #167

I would take your current marketing front page and make it the page for developers. Then I would work with a B2B SaaS marketer on what you actually need for the people who make the purchasing decisions. You made a great construction kit, now you need to demonstrate with actual app demos what you can make in an amazing way that your competitors cannot. Developers love making libraries and construction kits as a produc…

Thanks for the advice. Appreciate it.

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

#236
post #190

Earlier quoted context omitted.

The problem with modern development is having to nail down the data model first. I wish we would develop software where the data model could easily change. To do this every data dependency in the system needs to traceable. Nothing does this so far. And everyone just picks a database off the shelf but none are even remotely useful for this.

Admittedly, yes. This is the massive appeal of Mongo et al., or just JSON[B] columns in an RDBMS. Unfortunately, at a very deep level, that’s simply not how RDBMS works. The tuples are a B+tree, and in some (MySQL [InnoDB], SQL Server) cases everything is clustered around the PK. If you don’t create a data model that’s easily exploitable for optimizations designed around that data structure, you’re gonna have a bad t…

Nosql doesn't solve the schema migration problem. It just means you don't formalize your schema. But your code will implicitly require a certain schema anyway. Changing the schema means changing the code and migrating data. You'll have to write migration scripts and think about backward compatibility. Same problems as in sql.

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

#238

I love the idea. Will try some of it this week. Is there plans to have a linux offline client too ? (I use both linux and windows).

Offline mode should work on linux too. I only have ubuntu so that's what I tested. It's just service workers underneath, so if it's the first time you open the app, you do have to wait for a few minutes for it to download.

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

#239

Honest and genuine feedback. I am concerned that you may be working on something that does not have a market in its present form, or possibly ever. I am worried as to how much of your life / time / money you might be pouring into this. It is difficult for me to be categorical about this, as for all I know it's a tiny side venture and you're not bothered about adoption. But, based on the marketing copy / launch, previ…

I appreciate this feedback. Thanks for writing it out. You have some valid points here and I'll think about them going forward. 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.

In my time I have had a roughly 50/50 split between projects that failed and ones that took off.

The ones that failed tended to be 'passion projects' where I was led by what I wanted to do, or what seemed cool, and became obsessed with 'finishing' them to a high standard rather than releasing (or abandoning) them. One failure was a puzzle game for early iPhone (iOS 5 I think) - it took 6 months, but ultimately was far more fun to build than to play. Looking bad, I was kidding myself - it looked average at best, and there were far better people and games out there than the one I was building. I learned some fun things but I probably should have stopped after a couple of months, whereas I think I threw 6 months at that one.

The success stories were the ones where I was led more by a sense of market demand - e.g. there was a problem that needed solving, and I had some awareness that existing solutions either did not exist, or weren't a good fit.

I built one of the very first apps in the transport tech space and that was a big success, both in terms of adoption and profitability. That was a combination of skill and luck - i.e. 'right place right time'.

While I have now had 2-3 'success stories' in terms of products that took off / gained significant adoption, I must say I haven't fully learned my lesson and I do still have the same obsessive tendencies! Coding is addictive huh. I recently spent 3 months building a full stack React app that I just did because I wanted to "finish" it, and I'm not really sure if there is a market for it. But I had the time available and I think the older I get, the more I can self-police and know when it's time to step away.

Also, if you only spend a small amount of time on something, even if it doesn't get used, as long as you've learned new skills or experiences, then it might arguably have been worth it.

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

#240
post #190

Earlier quoted context omitted.

The problem with modern development is having to nail down the data model first. I wish we would develop software where the data model could easily change. To do this every data dependency in the system needs to traceable. Nothing does this so far. And everyone just picks a database off the shelf but none are even remotely useful for this.

Admittedly, yes. This is the massive appeal of Mongo et al., or just JSON[B] columns in an RDBMS. Unfortunately, at a very deep level, that’s simply not how RDBMS works. The tuples are a B+tree, and in some (MySQL [InnoDB], SQL Server) cases everything is clustered around the PK. If you don’t create a data model that’s easily exploitable for optimizations designed around that data structure, you’re gonna have a bad t…

Yeh RDBMS is probably the wrong choice for most apps. It was good for crunching sales data in batches back in the day. Everything today is pipelines and reactivity.

My dream is to have a tool to model my logical data model and then it will organize my data into the best storage and caches.

I don't think any existing database today is useful.

Post reply on HN