b2b-android-create-api

Android Kotlin API layer scaffolding is automated by providing domain, endpoint, HTTP method, and request/response structures. The tool generates Service, Repository, Entity, VO, and Mapper files with consistent naming across network and app modules.

Generating nullable Entity and non-null VO data models is handled automatically during API scaffolding. The process applies default mapping rules to ensure Entities remain nullable while VOs are non-null, enforcing consistent data modeling for Android Kotlin projects.

Dependency injection wiring is updated automatically during API layer generation. The scaffolding process modifies ServiceModule and RepositoryModule to include new Service and Repository components, ensuring immediate integration without manual DI configuration.

Paging and UseCase components can be generated optionally during Android Kotlin API scaffolding. By specifying the requirement during setup, the tool extends the base Service and Repository files to include paging support and UseCase logic.

Both v1 and v2 endpoint patterns are supported by the API scaffolding tool. Providing the desired API version alongside domain and endpoint information ensures the generated Service, Repository, Entity, and VO files match the correct versioning rules.

To scaffold an Android API layer using Kotlin, you need to provide the domain, endpoint, HTTP method, request and response structures, and the desired API version. This inputs allow the generation of network and app module files with KDoc.