:books: Android Sample App using modular, clean, s...

# feed

[Madalin Valceleanu]

📚 Android Sample App using modular, clean, scalable, testable Architecture written in Kotlin following the best practices with Jetpack.

The architecture of the application is based, apply and strictly complies with each of the following 5 points:

• A single-activity architecture, using the Navigation component to manage fragment operations.
• Android architecture components, part of Android Jetpack for give to project a robust design, testable and maintainable.
• Pattern Model-View-ViewModel (MVVM) facilitating a separation of development of the graphical user interface.
• S.O.L.I.D design principles intended to make software designs more understandable, flexible and maintainable.
• Modular app architecture allows to be developed features in isolation, independently from other features.
Link: https://github.com/VMadalin/kotlin-sample-app

[Sergio]

Thank you, great content.

[Mikołaj Karwowski]

Great stuff, I was looking for something like that.

Just a small thing, You've hyperlinked Coil to Glide in tech stack dependencies, here:

• Coil - image loading library for Android backed by Kotlin Coroutines.

[Mikołaj Karwowski]

Also... Where do You get crashlytics Public and private api keys, since it's on Firebase? 🤔

[Madalin Valceleanu]

You are right I use the wrong link for coil project, thank you @Mikołaj Karwowski

[Madalin Valceleanu]

Regard the crashlytics, the project keep use the fabric and it’s migrated to firebase yet. This is already added task to do 🙂

[Mikołaj Karwowski]

Ahh, ok. That's what I was kind of thinking of, but I got bamboozled since You've posted about it so recently.
I guess there's no need to say bout providing api-keys in "local.properties project root file"
When it should be (at least Fabrics) be in fabric.properties 😛

[Madalin Valceleanu]

I added it on local.properties to avoid to push this file to git, having all the credentials on the same file. On building time the file fabric.properties is autogenerated with the valued provieded for that the fabric.key and fabric.secret

[Madalin Valceleanu]

Now I will update the url of coil 😉, please feel free to comment any thing that you see

[Mikołaj Karwowski]

Sure thing! :)

Bout the properties files - I don't know if it's just my side, but the fabric.properties won't be updated with new local.properties if the file already exists.
That's where my confusion came from - as I didn't know it's generated 😛
But if that's not somehow related to my environment (could You check if it behaves same way for You?), then I'd consider it a larger flaw or a bug, as every change would need manually removing file from my project.

Maybe somebody will find that one helping when starting the project up for the first time 🙂

[Mikołaj Karwowski]

Ok, ok, I see it's made that way on purpose in the code. I'm still considering it quite a confusing thing to do tho. Also would consider throwing another kind of exception, NSFE isn't exactly what's happening

What is the reasoning behind it (not refreshing fabric.properties file)?