LeetDroid VS compose-destinations

Yes, I agree that there should be a way to explore problems and other features without signing up. I have already created an issue for it and will soon update it :) https://github.com/cdhiraj40/LeetDroid/issues/2

App link Github link here are some features: 📷 More than 1000+ Leetcode coding/programming interview questions on algorithms, data structures, database, shell, and Concurrency. 📷 Daily new Leetcode challenges are updated every now and then and you will get notified! 📷 Each Leetcode problem has a clean, detailed problem description along with their solutions and discussions! 📷 Reminders for every contest a day and 30 mins before the start. 📷 Each contest can be saved in G-Calendar so that you never forget. 📷 General Discussions with tags like "interview-questions", "interview-experience","study-guide", "career" ,etc. 📷 You can search any Leetcode problem quickly with its name or id! 📷 Problems are categorized by different levels, various topics, tags. 📷 You can see your user profile right in the app with no. of problems solved, acceptance rate, ranking, recent submissions, etc. 📷 Check all the past contest details with your rankings and rating in that contest.

This time is about navigation, when raamcosta ( https://github.com/raamcosta/compose-destinations) in jetpack compose

The biggest help of all by far was Compose Destinations. It takes away all the boilerplate of maintaining your routes. A simple way to not have to create all those routes yourself with placeholders etc, including deeplink patterns and all. It generates all of that for you in a typesafe way. Just check the basic example on GitHub or the dedicated documentation website.

Here is a great solution for navigation in compose. Actually this is what Google should have done in the first place https://github.com/raamcosta/compose-destinations

Compose destinations is another alternative: https://github.com/raamcosta/compose-destinations

Hey, thanks for sharing here. Do you mind sharing how exactly this library is different from this one https://github.com/raamcosta/compose-destinations and why one would use one over the other?

I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.

I can't recommend the vanilla compose navigation from Google, but the community has built others like compose destinations which is pretty good.

Compose Destinations