Ask HN: Choosing an entrepreneur's stack in late 2018?

Server, web, and 2x mobile is a very tough requirement to meet. If it's just CRUD stuff I'd settle on ReactNative for mobile and use either clojure or js (both have the same reach in this case, but arguably clojure gives you a more unified experience).

But if you're pushing the envelope on mobile I don't think you're gonna pull this off to be honest. Consider reducing scope if possible.

For me personally Rails for the backend and web frontend. React Native for the Mobile Apps.

If you have experience with a specific stack and are or were happy with it then you should take that one.

Take a look at the recently announced phoenix framework live view

I highly recommend vuejs for the frontend. I can't imagine I would make a webapp without it.

My backend is in c++, because I'm more fluent in it than any other languages. For database, I'm using mongodb. I heard bad sayings about it, but I decided to stick to it, because I like its programming interface, I think it's easier than using sql.

It depends on your exact requirements. If it's something crud based go with an established framework like Django or Rails. Both of these have mature communities, ample tooling, and aren't going anywhere soon.

If you're looking to simplify as much as possible from your own perspective, consider using something like Next.js so you only have to learn one language. But you'll have to make other choices, so it's a trade off.

I wouldn't go 2 native clients on mobile, but perhaps ionic framework instead.

I wrote a blog yesterday about the technologies that we consider as the best to build a MVP https://ideatostartup.org/blog/idea-to-startup/the-best-tech...

If you are into JavaScript, you should also check out : https://2018.stateofjs.com to know which JS technologies in general developers prefer the most.

Honestly, even though it has its problems, Meteor is relatively simple framework that will even spit out mobile apps for you. It's probably the least effort (i.e. lines of code) to get a halfway decent app out, and it's scaled ok well as time has gone on. It has a bunch of weird quirks though especially in how it manages data.

https://www.meteor.com

You might look closer at react-native-web. It's early days and React Native can be painful at times however it does offer the idea of using one codebase for both mobile and web. It does require some care, flexibility and thought in design and development.

For the API, look to PostGraphile for GraphQL on top of Postgres (and of course, if multi tenant, there is row level security which is the direction I'd go today).

Rails and Laravel are great for MVPs.

Clients have pushed me more and more in to Laravel. It has a great community and lots of great packages and tools.

(Similar to what railscasts was back in the day) laracasts.com

(Server setup and deployment) https://forge.laravel.com

SaaS (in a box) https://spark.laravel.com/

Envoyer (zero down time deployment) https://envoyer.io

Backend: .NET Core Web API

Frontend: Vue

Mobile: PWA if possible

What did you use to write code in? If you're starting from scratch or starting from some existing form of knowledge even though it might be rusty, it's still in there. All technologies have weight to learn them. When you're bootstrapping something in the wee-hours and you just want to get shit done stick to tried and true instead of re-inventing the wheel. The majority of apps are CRUD. In this case Rails, Django, maybe Express/Node will do more than fine. Only use a whole JS front-end framework if your use case needs it for day one. There's a lot of overhead to learning them.

I'm a fan of Laravel for the back end and vue or bootstrap for the front end for quick MVPs.

Depends what you want to build. Give more details on your idea. You can implement core components and outsource rest.

Backend API: .NET Core

Web Frontend: AngularDart

Mobile: Flutter

Is serverless too bleeding edge? I am grubbing around for something similar with limited IT skills; know almost nothing about node.js world regrettably. I see serverless django etc. being mentioned more often.

I am in a similar boat, going to try and kick off a side project during this xmas break. As others mentioned, you should probably consider reducing scope and picking one platform to MVP on. I was also planning on doing a multi-platform project, but after some thought, it felt like doing the MVP on mobile first would be best (for the project I have in mind, it felt like I could get more features, faster, into a mobile prototype. might be different for yours though). So I think I am going to try out Flutter, for a few reasons.

1. I don't like javascript. 2. It sounds like Flutter is working on adding web and desktop support, so it's possible that after I am done with the mobile prototype, that might be ready. 3. I am not much of a designer, so the fact that Flutter integrates easily with material components[1], feels like it will make it easier to get to a half-decent looking MVP. 4. I already know python, so don't really need to worry about server side code if I need it.

Another thing to consider, is if I had just focused on building something, rather than evaluating a bunch of frameworks, I would probably be half-way to a prototype by now. But because my project is more 'side-project' than 'startup idea', part of the fun is just kicking around some of these languages and frameworks. But if you are aiming for more towards the 'startup idea', probably best just to get started with whatever you are most familiar with.

[1] https://material.io/develop/flutter/

If you're choosing PostgresSQL, I would like to recommend 2 things: One is GraphQL and another one is Hasura, for real-time GraphQL queries. This will make your project really lightning fast.

Reference Links: 1. https://graphql.org/ 2. https://hasura.io/

Backend: GraphQL + TypeScript with Prisma on top of a MongoDB/PostgreSQL Frontend: React / React Native + Apollo Client

Then use 3rd-party services for the "standard" parts of your business logic (like Auth0 for authentication).

This stack allows to move incredibly fast on the front- and backend and really lets you focus on building value-adding features instead of dealing with complexity that comes from e.g. database workflows (Prisma) on the backend or state management on the frontend (Apollo Client).

EDIT: As a side-note, companies like Labelbox.com (raised 3,9 mio seed round) or Hyrecar.com (recently IPOed) are using a similar stack and have been vastly successful with it.

I'm in a highly similar role, and doing MVPs for billionaire investors and CXOs who want to push and test their side-projects on a monthly basis. My answer would be: the "correct stack" (the one to have maximum impact with minimum time commitment) highly depends on the business idea itself: is it database-heavy, network speed critical, big data, AI requirements, related to crypto, related to offline businesses, .... Efficiency of languages and frameworks mostly depends on the libraries of the language, not anything else. I'd be happy to jump on a call with you, let's connect, email me at jakobm@mit.edu and I'll share my LinkedIn and references!