How to use navigation with multiple screens(compos...

# compose-web

[Anant Kumar Gupta]

How to use navigation with multiple screens(composables) in compose web? (include animations and passing data)

[Casey Brooks]

I just released a new navigation library, Ballast Navigation which works with Compose Web. It’s a simpler navigation library and does not have any specific support for animations, but you can always use CSS transitions for page animations

[Anant Kumar Gupta]

okay i will try it, thanks

[Anant Kumar Gupta]

@Casey Brooks would you recommend me to build e-commerce web app using compose web?

[Casey Brooks]

It all depends on what level of risk you’re willing to take on for your business. As a technology, Kotlin/JS works pretty well, but there are some key things to consider before deciding what to use for your web app. It definitely has a lot of pros (Kotlin is a much nicer language than JS), but since it’s still an early technology there are some cons to it as well.

• Kotlin JS works pretty and is a nice way to make web apps for folks that don’t know JS very well. But if you have developers that already know web technologies and are comfortable with JS, they probably would rather just keep working with JS/TS rather than learning Kotlin
• Kotlin/JS bundles are considerably larger than what you’d get from a something like a JS/TS React app, and I don’t believe they support code-splitting. So your page will take longer to load than with pure Web technologies
• Kotlin/JS is still in Beta, it has not been officially published as stable yet, and we’re probably still a ways out from this
• Compose/Web is still using DOM and CSS to make your web page, and IDE support for this is not nearly as good as you’d get from React, JSX, or other web technologies in VSCode.
There are benefits and potential concerns for both Kotlin and traditional JS apps, and it’s ultimately up to what works best for you and your team.

[Anant Kumar Gupta]

so you mean in future compose/web won't use DOM and CSS to make web pages?

[Casey Brooks]

Work in in progress to run Compose Material UI on Skia canvas, rather than with DOM. DOM isn’t going away, it will continue to be supported. But it does mean that right now, even when building a Kotlin/JS web app, you’ll still need to dip into traditional Web technologies like CSS

[Anant Kumar Gupta]

well, our team knows kotlin very well, not too much idea about web development (html,css and js). so, should our team go with the compose web?

[Anant Kumar Gupta]

Now i'm very confused what our team should use, i found many ways to build web apps like Kvision, fritz2 & doodle.

Please suggest me which one should I go with

[Casey Brooks]

Yes, there are lots of options out there, and they’re all great in their own way. I could give you my personal recommendation, but honestly that doesn’t mean all that much. The choice of what technologies to use is ultimately the one that you and your team like best, that also delivers on the business solutions you’re working toward. And some random person’s opinion is not likely to account for all the things your team will need. There are many times in the past that I’ve adopted a technology because I saw people saying it was good, only to find out that it was actually a terrible choice for my particular situation (the GreenRobot Event Bus library on Android, and MongoDB, for a couple examples).

What I’d recommend you do, is have your team build out PoC applications in some of these Kotlin/JS frameworks, then discuss with your team the things your developers liked and didn’t like about each. Then weighing those preferences with the known requirements of your app, you will be better equipped to make a more informed decision about which one to move forward with.

[Anant Kumar Gupta]

Actually i have to submit my college final project of e-commerce. I would love to check all those technologies but I don't have much time, that's why i asked you to recommend me which option i should go with. Thanks for your support❤️.