[HN Gopher] Show HN: Nextless.js: Full-Stack React SaaS Boilerpl...
___________________________________________________________________
Show HN: Nextless.js: Full-Stack React SaaS Boilerplate with Auth
and Payment
Author : creativedg
Score : 42 points
Date : 2021-07-28 14:55 UTC (4 hours ago)
(HTM) web link (nextlessjs.com)
(TXT) w3m dump (nextlessjs.com)
| tlackemann wrote:
| Your main competition is going to be Laravel. And they're a hell
| of a lot cheaper, better supported, bigger community ...
|
| What's the strategy here?
| willio58 wrote:
| Not really, this is like a full-on boilerplate with multiple JS
| frameworks, templates and all while Laravel is really just a
| PHP web framework (from my understanding). If someone created a
| boilerplate SaaS product with Laravel, I think that would be
| more comparable.
| tlackemann wrote:
| Admin Panel[0] Subscriptions[1]
|
| Anything you can think of, chances are there is not only a
| PHP package for it, but probably an out-of-the-box Laravel
| package.
|
| Whatever this is, it won't beat Laravel.
|
| [0] https://nova.laravel.com/ [1]
| https://laravel.com/docs/master/billing
| arcosdev wrote:
| it's not PHP
| cutler wrote:
| You think clients care?
| mynegation wrote:
| Clients may not care but the founder or development team
| may.
| calvin wrote:
| The CTO and security teams and devs will care. The language
| decision has a broad impact on how to secure the
| application, engineering community (who can you hire), etc.
| It's a big decision.
| tlackemann wrote:
| So PHP should be the obvious choice then, considering
| what a bloated mess and security nightmare Node.js is.
|
| As someone who ran a company for 5+ years on a Node.js
| stack, never again.
|
| Before when I managed 5k+ servers running PHP, I actually
| slept at night knowing nothing was suddenly going to go
| wrong because of some stupid memory consumption bug or
| exploit in a popular and critical package.
| vosper wrote:
| I think if you're starting up today you may find easier to
| find someone who can build you a site with React than with
| PHP. Or if not today, then give it a few years.
|
| Likewise I think someone starting up for themselves is more
| likely to be a React programmer than a PHP programmer.
| MisterBastahrd wrote:
| I think it's hard to fine good PHP developers.
|
| I also think it's damned near impossible to find React
| developers who are capable of doing anything that isn't
| React flavored.
|
| For those reasons alone, I'd choose PHP over React,
| especially if I want to scale.
| tlackemann wrote:
| This is such a stupid, stupid argument. Anyone who makes this
| argument has clearly never written PHP or has some personal
| stake in the Node.js ecosystem.
|
| I've written Node.js/Javascript/TypeScript for the past
| 5-years and my last few projects have been Laravel just
| because of how damn easy it is. I've used Next.js, Gatsby,
| [insert flavor of the month here], but nothing has stood the
| test of time like PHP has. I never had a PHP server die on me
| because of a lost network connection. I never had a PHP
| server kill thousands of connections because of one error. I
| never was 4 versions behind a framework because it changes
| every fucking week. PHP never had me deploy a Kubernetes
| cluster with seven thousand pods and monitoring systems just
| to stay alive.
|
| Node.js is a horrible programming language with a worse
| package system and anyone who thinks otherwise hasn't had the
| privilege to work with something else.
| leerob wrote:
| Related, free template: https://github.com/vercel/nextjs-
| subscription-payments
| cjonas wrote:
| Can someone explain the advantages of using nextjs serverless?
| cjonas wrote:
| Sorry to clarify... I understand the benefits of serverless,
| but what does nextjs add beyond just built in routing. Seems
| like most of it's benefits are part of the server
| BerkhanBerkdemi wrote:
| I see similarities with Redwood[0]. Nextless.js is just added
| sugar, spice and rest of the boilerplates.
|
| [0]: https://github.com/redwoodjs/redwood
| robertlagrant wrote:
| This is a great idea that I wish I'd got stuck into doing when I
| thought of it :) Very nice.
| magicink81 wrote:
| You're not too late. Do it! You'll learn more along the way.
| You don't need to be first, you just need to be good.
| a13n wrote:
| I've thought a lot about this specific idea.
|
| I think the problem with your business model is:
|
| - People who have already built their company/website/product are
| not going to move the world to adopt your platform. It's just too
| much work.
|
| - This leaves you with people who haven't built/shipped anything
| yet, who aren't really willing to pay $500-2000 for your software
| (there may be exceptions, but not thaaaat many).
|
| I think a really successful business model would be something
| like:
|
| - Free for the first $10k revenue
|
| - 3% of revenue after that (auto calculated via Stripe)
|
| This way, many more people will get started with your software,
| and those that are actually successful will end up paying you a
| lot more than $500. "We don't get paid till you do" is the
| headline on your pricing page.
|
| I'd imagine your retention would be amazing because it'd be very
| difficult to move off (similar reasons as Stripe, AWS).
| arcturus17 wrote:
| This could be interesting for agencies and freelancers more
| than the customers themselves.
|
| I own a consultancy and I might find this interesting as I
| don't have an internal SaaS framework yet.
|
| The two problems I see are:
|
| 1. Lack of options... There may be some parts of the stack that
| I don't like or don't fit requirements
|
| 2. Unknown code quality... Cannot tell what the coding
| standards are. This is related to #1 in that I don't know how
| hard the code will be to modify unless I read it.
|
| Otherwise it's an interesting proposition. React/Nextjs are my
| jam, and I prefer serverful (Django) to serverless but that
| might be negotiable. But even if I wanted to drop in my own
| server, if the front-end is well coded I could easily save
| 2x-3x the 1.8k sticker price in dev costs on a single project.
|
| If I were to build a SaaS myself, I might also find this
| interesting with all the caveats above, but I would 200%
| certain not pay a revenue share unless the platform really
| required minimal tweaking and was about 90% adjusted to my use
| case, and provided continued platform value after that launch
| (like, say, Shopify).
| madjam002 wrote:
| Stripe offers self serve customer portals for managing
| subscriptions out of the box with their Billing offering, plus
| checkout pages, so it's super quick to integrate Stripe into your
| own project now with minimal boilerplate.
| teamspirit wrote:
| That's what I was thinking. For this to succeed, they'd have to
| differentiate themselves from Stripe's own offering and, at
| least to me, that's not obvious.
| devops000 wrote:
| We can do similar with Webflow, or Bubble.
| creativedg wrote:
| I'm not an expert about Webflow, or Bubble. But, if I'm not
| wrong, I don't think you can build a SaaS with these two nocode
| tools.
| ctoth wrote:
| This looks nice but you might want to read over the site for
| spelling issues.
| creativedg wrote:
| My fault, I've already tried to fix the spelling issue, I've
| done my best. As you can see, English isn't my mother tongue :s
|
| I'll seek the help from a native english speaker.
| patatino wrote:
| Just use supabase + nextjs + stripe
|
| They have a free example on their page, covers most of what this
| is offering
| cutler wrote:
| $2099 plus licence fees for each client? Good luck with that. I'm
| assuming the client licence fee is the Single licence at $699 but
| it's not specified.
| vittore wrote:
| There are good amount of rails starter templates that going
| around that price with similar set of features. I think there
| is demand for it. (not affiliated with it in any way)
| cutler wrote:
| Do they have additional licence fees for each client as this
| does?
___________________________________________________________________
(page generated 2021-07-28 19:01 UTC)