This is a Kotlin Multiplatform (KMP) library that provides GraphQL network integration and data fetching repositories for Guardian Feast client applications on both Android and iOS.

It encapsulates network communication, Apollo GraphQL query execution, response parsing, and exposes clean Kotlin coroutine / Swift async interfaces and Koin dependency injection modules.

---

• GraphQL Integration: Manages GraphQL queries, operations, schema mapping, and serialization.
• Repository Abstraction: Exposes high-level data interfaces (GraphQLRepository) so client apps do not need to deal with GraphQL queries directly.
• Cross-Platform Delivery: Delivers Android AAR/JAR artifacts via Maven and iOS frameworks/Swift Packages via XCFramework.

• backend:graphql: Internal module containing Apollo GraphQL configurations, generated query models, network execution logic, and endpoint providers.
• backend:api: Public-facing entry point exporting GraphQLRepository, platform-specific DI initialization functions (androidFeastApiModule, iosFeastApiModule), and Swift wrappers (FeastIos).

backend uses an independent versioning lifecycle from the root library module:

• backend Modules (backend:api & backend:graphql): Versioned independently via backend/version.txt (currently 1.0.0-alpha01), following Semantic Versioning (SemVer) suited for network and API contract releases.
• library Module: Uses root version.txt corresponding to unit conversions and recipe scaling domain rules.

---

This section will be filled once we have a release YAML file ready in the CI pipeline to publish to Maven Central.

Follow the steps below to publish the backend library to your local maven repository(run command in terminal at the root of the project):

1. Gradle sync to make sure all dependencies are downloaded

1. ./gradlew graphql:publishToMavenLocal
2. ./gradlew api:publishToMavenLocal
3. Published artifacts can be found in ~/.m2/repository/com/gu/feast-multiplatform-api/<version> and ~/.m2/repository/com/gu/feast-multiplatform-graphql/<version> respectively.

Both need to be published for Android. We have defined the :api dependency in the consuming app. :graphql is pulled automatically by Gradle when building - but it still needs to be available independently on mavencentral/mavenlocal.

1. ./gradlew api:assembleFeastMultiplatformBackendXCFramework
2. The XCFramework can be found in backend/api/build/XCFrameworks/release/FeastMultiplatformBackend.xcframework. You can copy this framework to your iOS project and link it manually.

We don't need to publish the :graphql module for iOS, as it is only used internally by the :api module and also exported in api module's XCFramework.

This section will be filled up after confirming or by an iOS develper

Consumers only need to depend on backend:api. Transitive dependencies (including backend:graphql) are bundled automatically via Maven POM metadata:

// build.gradle.kts (module level)

dependencies { implementation("com.gu:feast-multiplatform-api:") // e.g. 1.0.0-alpha01 }