I work async and communicate via screen recordings a lot. Loop and other softwares felt clunky with their litlte windows obstruction on every window change/reboot.
So I built a simple in-browser screen recorder with basic editing and share links that expire in 24h. Cloudflare R2 giving free egress allowed me to make it free.
I also did the same, built my own analytics with TinyBird for one of my projects (https://linkycal.com). It ended up costing less than paying for a hosting provider
I am not sure what you are trying to say here but if you can find a way to make something like this with a tailwind-whatever-the-fuck, please let me know because I need it too.
- I have 154 active users as of now.
- I had the Pro sale running since January starting as a new year sale, it was at 20 now 11 left.
- I have been building the project for over a year on and off. Everything is made by myself. Scheduling, messaging, page builder, etc, I am not launching off of a template.
If you are actually a developer, you should know these things are not that npm-install easy.
I have used both SvelteKit and React. Dev velocity was great in the beginning with SvelteKit when everything was super simple but decreased drastically as the project grew. Went back to Next. Apart from devs, none really cares if you wrote it in Svelte, React or bare HTML/CSS or if your site loads double digit milliseconds slower.
My app had about 50 routes (by the design there were about 80 pages, but of course some common patterns emerged). I wouldn't call it large, but it's past "toy" and probably not "small" for most.
I didn't have a problem, so I'm curious what the previous poster ran in to.
the only thing I can think of is that it doesn't impose much structure on the "lib" folder -- that's where code/components that aren't directly in the route files go. But there's nothing keeping you from keeping that organized yourself. So that's not really a problem, but something you might want to think about early if you plan to build out the app in the future.
I have tried to use sveltekit once and turned around in 20 minutes as routing is severely limited. All I wanted to do was to route based on domain, with a different set of routes for one of the domains. Not exactly complicated or uncommon, but not something you can do with the sveltekit router.
This is gone over in the github threads about such a feature - basically, as two different projects semantically, the best thing is to create two different projects physically, in a monorepo. All the code-sharing with none of the additional complexity.
As for routing, I guess that gets unmanageable pretty fast. Just in the sample blog tutorial here [0], you get confused with the number of files and nested folders that has same file names as level above.
Thing I learned through experience and also from other people is always do the bare minimum when starting a project like this.
You should be able to get away with low code/templated websites for most cases. No need to build mobile apps unless it's absolutely necessary, like when it wont work without native apis.
Also Rob W says dont start a marketplace if you dont have one side already figured out
