Parse Android SDK vs. using GraphQL with Apollo

[cbaker6]

@L3K0V

I’m not sure about who will gonna use it at it should be used via JNI and the footprint as I read is 35mb because of the core libraries which are bundled.

You might be right, I’ve heard swift builds on Android tend to be large. My original goal is to get a basic build for CI to make sure the SDK always builds for Android.

@L3K0V

Do you have something particular in mind with this Swift build for Android?

Get a basic build for Android, similar to the Linux build

@L3K0V

I think the more suitable and standard way is actually writing everything in Kotlin using multi platform module (KMM - Kotlin Multiplatform for Cross-Platform Development | JetBrains) and build both Swift and Kotlin libraries to be consumed

This could work. I don’t know much about Android or Kotlin, but from what I understand there needs to be some underlying framework Kotlin would need access to. The JS and Swift SDKs seem to have the most up-to-date features with respect to the server. Flutter seems to be next, but doesn’t have adequate CI testing. The Android and iOS SDKs have the fundamental features, but are missing a lot when compared to JS and Swift SDKs.