![]() ![]() Twelve months later we now have 7 APIs using Kotlin Serialization for JSON parsing, these models are published to our Enterprise Nexus Repository and used by our Android App - this represents about 20% of all the APIs used in our App. ![]() We were never really sure about our strategy to share our API models with our clients would really work not because it was a bad idea but because we knew it would be difficult to get buy in from our API developers. First of all, in your project-level build.Continuing on our journey from the article “ The first steps on your Kotlin Multiplatform journey - changing your microservices” that I wrote last year, I wanted to give an update on our progress and share some learnings. So to use Kotlin Serialization in your project you'll need to add some dependencies. There are definitely other reasons that you might want to use serialization, like for decoding JSON responses from an API. I actually used Realm in the past for this specific project and I ended up overengineering and migrating back to SharedPreferences eventually anyway. ![]() ![]() In my case the data is really simple and it's a small set. If you have a complicated, large set of data you really should be using Room or Realm - or something else along those lines. In my specific case I had a data class that I wanted to save to SharedPreferences. There are a few reasons why you might want to use Serialization. I'm going to specifically write about JSON serialization. Today I thought I'd write a quick post about using Kotlin Serialization in an Android project. Android, Serialization, Kotlin - 1 min read Using Kotlin Serialization in an Android Project ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |