Why Using Navigation-Compose in Your Jetpack Compose App is a Bad Idea | by Patryk Kosieradzki | Feb, 2022

Photograph by Markus Winkler on Unsplash

Podcast!

  • /customers — for the person record display
  • /customers/2 — for the element display for person with id = 2.
  • Path params — /customers/arg1/particulars/arg2
  • Or to make it much more sophisticated, you can too move question params and elective parameters after the query mark — /customers/arg1/particulars?arg2=arg2_value&arg3=arg3_value
val urlParam = "https://translate.google.com/?hl=en&tab=TT"
navController.navigate("path/arg=$URLEncoder.encode(urlParam)")
URLEncoder.decode(bundle.getString("arg_key"))

Enums

Parcelables and Serializables

Is there something we are able to do?

Replace

Explanation why it is best to nonetheless use Fragments

After all, Fragments aren’t excellent. What points with them must you think about on this case?

More Posts