On the plus side:

1. Good UI. Skaffolder has a really great UI and CLI to, well, scaffold an app. It lets you go fairly in-depth about how you want your data tables structured and related, how the API looks, and what the app pages do. This is not an easy thing to do well, and Skaffolder strikes a nice balance between too many options and not enough.

2. Ease of use. Some may argue about this, but I take issue with the questions suggesting Skaffolder make database relations easier. I'm a software developer. There's a lot to know in building an app, and I don't see how Skaffolder could hide the fact that there are multiple tables with related keys between them and still have a useful product. When an app has more than one "entity," when it deals with lists of several different things, there is always the complexity of relationships. Where Skaffolder shines is that I can, for instance, show my wife how to define tables and help her link a few and she'll be empowered to create more on her own.

3. Freedom from scaling costs. Skaffolder generates the source code for your app. You can deploy it where you want at whatever scale you want. You'll pay for the extra hosting and bandwidth, of course, but that's a bargain rate compared to what many mobile app services charge when you scale.

Now for the downsides:

1. Skaffolder gives you a great start on an app, but you're going to need some skills to polish it up and to host it. These "disadvantages" are just the flip side of the benefit of getting source code and an app structure meant as a scaffold. It doesn't offer a graphical tool for designing your app pages in detail, and it doesn't give you the bloated app such graphical no-code tools give.

2. Skaffolder has more templates, it seems, than they can maintain. The number of options is exciting! You can generate your app code in so many different technologies. But it takes a lot of labor to make sure those templates stay up-to-date. The React + Sequelize app, for instance, uses several old or deprecated libraries. Skaffolder-cli throws audit errors when installing and a deprecation warning (DEP0148-deprecated folder mapping in exports) whenever it runs. The Sass in the generated app requires a native library that won't build on my M1 Air.

So...it's a fair tool. I'm curious to see where it goes. Some of what makes it complex also makes it great. Some of the templates could use some revamping.