we are writing book about Android Development with Kotlin for Packt, and we've decided that there needs to be app that will show how all introduced Kotlin features can work together. Points are:
* It cannot be long, while it needs to described in 20-30 pages chapter. It wasn't planned previously and now we don't want to make this part to long. Also, it should not be complex and it should use only simple and standard dependencies. I decided to include RxJava, but I am using only most basic features, which are easy to explain.
* It should show as much Kotlin features as possible. But they need to be used in good way (reasonable).
* We want it to look good (visually).
* We would like structure to be simple, but also clean, because readers might later use it as reference in their own projects. This is why we've decided to implement it in MVP.
We've decided to make Marvel gallery basing on Marvel API, because it have nice pictures and everyone likes superheroes ( at least I do xD )
I placed code proposition here https://github.com/MarcinMoskala/MarvelGallery
We need as much feedback as possible. And every opinion is valuable. Packt is a big publisher, and this book will get to lot's of people. For most of them it will be first contact with Kotlin. And your feedback can make it better. But please, write on priv. I don't want to spam this group.
06/12/2017, 6:32 AM
marcinmoskala: Since you want users to use this project as a reference, why don’t you use Dagger 2?
06/12/2017, 7:17 AM
It suppose to be simple. I want to avoid dependency injection explanation in book. I am also not sure if it will be used in future in Kotlin.
I also wanted to avoid RxJava usage, but I needed mapping from DTO to model and automatic repetition (Marvel API is not always working in the first time)