There is no doubt that people are getting away from GSON and I agree with those reasons too. The only advantage GSON has over other parsing libraries is that it takes a really short amount of time to set up. Furthermore, the most important thing is that Moshi is embracing Kotlin support.
First let's implement the dependency:
It's not a struggle to migrate to Moshi. It's really Gson look-a-like. The only thing to do is annotate the object with @field:Json instead of @SerializedName (which is Gsons way for JS representation):
Apparently, in order to solve a problem we are done, but we haven't unleashed the full power yet. Remember, this way we haven't still yet implemented the Kotlin support. With this, Moshi comes with some new dependency to add and an annotation processor for generating the adapters. Refer to the docs for more:
In Java, we have the transient keyword in order to use optional values for Moshi, while in Kotlin this is achieved though a @Transient annotation:
If you notice more, the @field:Json is now just a @Json. And we have annotated the class with @JsonClass which helps the class to be encoded as JSON format
If you skipped the reasons why migrating from Gson to Moshi, I'm giving my own reason
- Speed (I immediately noticed that even though in debug mode).
- Kotlin support.
- Proguard rules: If you choose only the Java version of Moshi, you won't need any pro-guard rules for release builds.
If you find reasons not to like Moshi, I suggest take a look at Kotlinx Serialization. IMO, it's a little too early to use it, but it surely looks promising.