• 0 Posts
  • 3 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • I’d say the ideal thing to aim for is case 2-ish. Building in isolation isn’t great and dog-fooding your lib (via their projects) can help reduce the amount of future breaking changes (getting things right the first time). I.e. Ideally your helping people upgrade when needed and seeing their problems. Even if your forking their projects to try your experimental changes out for them and then provide a PR? That’s probably a lot easier said than done though xD

    A dependecy management system to let consumers know when a new version is available could go a long way, or you pushing for them to update by talking to them (as this is all internal?).

    Basically reducing the distance between teams and getting the tightest possible feedback loops should be the goal.

    That’s my rushed 2p while waiting for a haircut anyway ;)



  • Haha! I too have wanted to do the same thing! Well… not in React - I actually wanted to use leptos because it seems neat. So ideally I’d want an API client that’d work in rust in wasm. Or maybe it’s simple enough to migrate an existing one over.

    As this is very likely just a side project for me, I may as well share my desires for any new client. One thing I’d really like to see in a Lemmy UX is a swipe based navigation like in Sync for reddit. Such a lovely way to navigate.

    Oh oh! and some decent customisation on different views (depending on communities and whims). Like big cards with previews and smaller ones with title emphasis.

    Tbh all of this is basically what Sync had. Sync was great…

    Not sure if making mobile apps these days is required as web apps can get you pretty much there with service workers etc. I guess hosting is still the main issue even though offline first apps can mitigate that a lot!

    Thank you for reading my rambles. It’s pretty much a mind dump rather than being directed at anyone etc :)