How To Implement The Event Bus Pattern With Kotlin SharedFlow In Your Android App

[@markusmcgee]

using this tonight lol. Need to knock out POC by tomorrow. This is part of it.

[@yanneckreiss]

Good luck, you can do it 😎👍

[@willi11319]

amazing, keep up the great work!

[@radbaver]

Amazing content! Thank you for sharing your advice with the community :)

[@andresromerodev]

This is awesome, thank you!

[@subindsuresh4897]

Thank you bro.

[@count7ero]

i still endorse the old event bus over just about every other pattern. apps have increasing richer and richer widgets that peek at multiple types in the model i.e. an update to a type in the model has an impact in multiple widgets in multiple screens. and you dont know which one will be the first to request an update (the app will not always open by user clicking the icon!!!) e.g. you have a friend list in a friend screen, but on the main screen you may have a menu "Friends 145", a wild notification "12 frends are interested in x" etc. i would never use observable pattern because it short-circuits the response to the source of the request. and to implement this pattern over and over, i would call this much more verbose actually. i would maybe only use observable/livedata/rx if i am bursted updates through a websocket and i consume them all in one place e.g. a list of stock tickers

[@EmanNollase]

awesome!!

[@nfaical3]

Thanks Can you share the source code ?

[@rockerxillodiego]

nice