Just an idea
Just an idea
Just added the Apache License.
Goals:
My current goal is to just get the site working with all/most of the existing functionality. For that there is a lot to do. Profile/settings page, comment replies, community browser/subscriptions.
Just did some reading and it indeed does seem like GPL is not allowed in app stores as it does not allow any further restrictions (such as Apples store's requirements).
I have to do some research.
It seems like GPLv3 is ok. https://en.wikipedia.org/wiki/List_of_free_and_open-source_iOS_applications https://github.com/tigase/siskin-im/issues/103
Updated
lemmy-js-client library you are using is licensed under AGPLv3. So I'm not sure if you are allowed to use it with your current license. You might have to make your project AGPLv3 too.
AGPL is a Copyleft license, so how can it be possible to use such library in an Apache licensed program? Isn't the whole idea of Copyleft to make that impossible? To make sure that nobody can take away users freedoms?
I think what they meant on gnu.org is that you can use Apache licensed code in a GPL licensed program.
Single codebase for web, native Android and iOS apps. This is possible with Svelte + Capacitor.
Interesting. Is this easier to work in than React Native?
I like that you chose Sveltekit, and the project structure seems pretty good. But there's a lot to fix. The page load takes way too long (you should be using #await whenever possible), and the design is very messy.
If I may suggest, I think you should be using a UI framework. It will keep you in-line, and give you good defaults, and maybe even save you time. I feel like Carbon is a good match for this sort of app. But If you don't like it, Skeleton also seems like a good choice.
Also, imho you should be using display: flex a lot more! (or grid)
Either way, I like the initiative. I might be able to help out a little bit here and there, but I can't make any promises.
Good luck!
My coding style has always been to get out the core functionality then fix everything up, definitely not for everyone. Might be something I need to reconsider when working with others.
I love carbon, but I chose Ionic is because its very suited for mobile development. On the other hand it seems to have very severe limitations for mobile so it seems I have to pull in something else in as well.
The page load takes way too long (you should be using #await whenever possible)
I will, though part of the reason its slow is because its hitting lemmys backend over the network, as opposed to just a local network in a normal setup.