saasform VS Svelte

Saasform: https://github.com/saasform/saasform

I had to prioritize another project (solokeys).

I still really believe both: 1) in an open source alternative to auth0, 2) in combining auth+payments for saas.

However, because they’re two problems, it’s probably best to focus on just one. For me trying to launch Saasform the issue has been to find and onboard customers quickly and at scale.

I also purchased Landkit, but eventually found it very heavy. I then essentially remade it on top of Fresh [1]. Code is here if anyone needs it [2].

[1] https://github.com/cssninjaStudio/fresh

[2] https://github.com/saasform/saasform/tree/main/data/themes/f...

If it's a web saas, we're building Saasform [1] with your use case in mind.

One relevant example is launching your MVP as a serverless API (e.g. on Firebase) + react/vue front end. Just iterate on your core product and features, we handle home page, registration and payments.

For mobile apps I'd recommend Expo [2] and, if you can, stay with their managed flow. If you want to iterate fast, you need to take into account the time to release to the stores and Expo can help with that. Similarly as for the web, I'd look into a serverless API model to start.

For email notifications I'd go with Sendgrid.

I personally never used no-code solutions but different people recommended Bubbles [3].

[1] https://saasform.dev

[2] https://expo.io

[3] https://www.bubbles.io

Starter kit to "transform your project into a SaaS", with auth+payments.

https://github.com/saasform/saasform

Saasform: shameless plug, this is my project, modern (at lease I hope), written in typescript

We are also doing something like that lol. It's a crowded field I see. Of course any cross contamination of PR is more than welcome :-)

I made this exercise to guide myself throught the process of starting from a list of features, summarizing benefits, prioritize them, sparkle some keywords and finally output a marketing page.

Working to make a marketing/public site for a micro-saas I was building, I realized there's plenty of articles about the structure of the landing page, sticky header, include quotes, etc. but there's little on how to actually write the content. I worked w/ different marketing professionals in the past and, though everyone has their own style/processes, the tldr is "talk about benefits, not features".

If you're making a marketing page, I hope you can find it useful too!

Please lmk if 1) the exercise makes sense to you, 2) the format is clear/unclear - what can be improved, 3) should I maybe write an accompanying blog post? other ideas?

For context, I expect to launch a number of micro-saas in the next months, so I wanted to build a repeatable process. I then plan to run all these sites out of config files like this [1].

[1] https://github.com/saasform/saasform/blob/main/data/config/w...

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.