Develop Node.js applications without spending time on repetitive coding tasks
github.com
github.com
On the home page, the benefits for a full-stack developer is that it sets up a boilerplate for you using Nest, Prisma, GraphQL and with built in auth. However, this just seems like any other boilerplate but without the extra complexity and pricing plans. It's not hard to set these up. Plenty of official documentations for these integrations.
My problem with this approach as a FS developer is that whenever I want to fix nasty issues or do something more customizable, I have to dive into the autogenerated code. In other words, I have to learn how things work anyways. Why not just set it up myself so I know exactly what's going on?
The pricing plan is also a bit confusing. It charges based on the number of developers, IE $200/month for a team of 10 developers. But if you have 10 developers, you most certainly have the time and expertise to set up a custom server with the same functionality and without all the magic.
For a front-end dev, it advertises that you don't need to write a backend because it generates one for you. But if you don't know how to write a backend, then you should stick to something like Firebase or Supabase. Otherwise, you might have to dive into gnarly Nest.js dependency injection syntax, Prisma, and auth eventually.
About the users - we are building Amplication for pro backend developers. The code we generate is built based on best practices with well-known technology, so it does not require learning anything unique to Amplication.
Also, we provide several ways to customize the code without breaking the link to Amplication so you can add business logic and customize your server with minimal conflicts.
When you build your server with Amplication, you get the server with all your data models, DTOs, and more so it saves you a lot of writing.
We are working now on a new version that will allow you to build microservices with or without databases, with or without queues and message brokers. And on top of that, we will introduce a plugin system allowing teams to use their own best practices and standards for the generated code.
Would love to get your feedback or any suggestions or ideas you may have.