AdventOfCode2019 VS saasform

I've been (slowly) doing Advent of Code 2019 on an STM32F303 microcontroller. I want all of the problem data to be stored in the binary, with the answers being output on a display. Most of my time so far has been spent on getting the clock working, and compression/decompression. I only have limited space (256KB), and the 20 of last year's problems I solved take up 221KB, so I decided the best course of action would be to store them compressed when possible.

I did consider just using compression library, but decided against it partly because it would be more interesting to write it myself, but also having a quick look I couldn't find one that could do decompression without needing additional temporary storage. It's not that fancy, just LZW with a multi-stage compression to optimize the dictionary.

Because of how many of the inputs work, you can often handle it in smaller chunks (e.g. one line at a time, I called them records), so the inputs have a small amount of pre-processing on my PC to split them up into smaller chunks so the entire input doesn't need to be held in RAM at once.

Of course, not all input data will compress well, some will even "compress" to a larger size, so I've also abstracted over the data storage so that it can handle reading records from compressed or uncompressed inputs.

I've done 4 days so far, and none of the inputs have compressed. Total runtime is 3.24 seconds (that day 4...).

Current state can be found here for the morbidly curious: https://github.com/Measter/AdventOfCode2019 Spoilers are in the mcu/src/challenges folder.

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...