Thinking in Compose with Epoxy | Android 2022 | Kotlin

This episode introduces a different way to consider building user interfaces. With the declarative nature of Epoxy (RecyclerView impl), we can start to more easily think about how our design translates to a Compose-like mentality! I do apologize the video is quite long, but I think it is worth the context. UI implementation/deep dive starts at around the 17:00 mark -- hope you learn something!
Don't forget to subscribe and enable notifications to stay up-to-date!
Full playlist here: • Season 10: E-commerce ...
Source code here: github.com/the...
API: fakestoreapi.com/
-- Popular Series --
Rick and Morty app: • Season 6: Rick & Morty...
-- Connect with me --
LinkedIn: / domenic-polidoro-802b72b4
Twitter: / developer_dom
Instagram: / dom_polidoro
Tiktok: / building_android

[@sarabjeetsinghhora7751]

EXCITED!

[@TheAndroidFactory]

💯💯 hope it makes sense!

[@McMouse88]

10:23 Kitty has made some noise ))

[@TheAndroidFactory]

Hahaha yes sorry my mic pics up their noises a little bit 🤣

[@RFbcc]

You're doing great! Keep it up!!! 1111

[@TheAndroidFactory]

Thank you thank you! Love the code 🙏

[@LE-rk7xu]

I learn a lot from your tutorials , thanks.

[@TheAndroidFactory]

Happy to help :D

[@TheAndroidFactory]

Anything you want to see specifically?

[@LE-rk7xu]

​@@TheAndroidFactorymaybe some animation or compose tutorials ?. sorry, my english is not good, i just use google translate :D

[@TheAndroidFactory]

Compose is coming soon! Animations good call :)

[@kineticgoat]

1111. Yay Compose!

[@TheAndroidFactory]

❤️❤️❤️ thank you for the support 😭

[@adi6564]

1111, your videos are amazing, I've watched most of them. Is it a good idea to use the Store like in this season to select specific values from multiple database tables, and then display them as one item? To use this season as an example, you'd get the product image from one table, price from another, and title from another, and display them like you did in the product list.

[@TheAndroidFactory]

This is often how real systems work. Not all the data is in one place and the backend knows how to merge the different rows to get the entire model you're looking for. For our case, that is a little complicated, but you could imagine the "is in cart" or "is favorited" information to exist in a different table and we "merge" them together to see our final product. Anything that exists in separate places in the store, could be seen this way as well -- kinda like an interesting way to build a relational database. Thank you so much for following along!! Love the support and happy it is helping you 😊

[@adi6564]

@@TheAndroidFactory Can you do an example of how to use the MVI architecture with a local db? It's helping so much! You're the only person that I found who has tutorials with Epoxy, and I love how you have different seasons that are split into clear subjects, by season and by episode. That way I can go back and rewatch and try to adapt what you're doing in the videos to my code, and there isn't distracting filler or irrelevant content on the way.

[@TheAndroidFactory]

Love the feedback!! Happy you are enjoying the way I've structured things :) that wasn't by accident haha Epoxy is wonderful and I have noticed I'm the only one with solid content. Hope that helps the exposure a bit! So I don't want to add room or something to this season, but that is an interesting request. You could just have your LiveData come straight from the DB as opposed to the store, and as you update the DB that would trigger an update in the observer. It's basically what I am doing with the Store, but I get to work with a Kotlin data class instead of a database.

[@farshad462]

1111 and do you recommend us to learn Compose?

[@TheAndroidFactory]

Thank you for watching it through ❤️ and yes, absolutely. But you should learn it once you feel comfortable with everything else in Android. I think I'll make some videos soon-ish on it, but likely not for a few months still

[@MrSojek]

Do you use Windows at work?

[@TheAndroidFactory]

I actually do not. For years I've used MacBooks at my companies and quite like them. This is just my personal desktop which I do everything else on - personal projects, KZbin, gaming, etc!

[@neyasbit]

I think there is too much logic in the fragment that is not related to this layer. It would be nice to transfer something to the viewmodel, something even higher

[@TheAndroidFactory]

Yup. We can definitely clean that up. Might be a good idea to now sooner rather than later.

[@nauruzguliev3489]

1111

[@TheAndroidFactory]

Love the support 🙌🙌