Challenge Overview
Challenge Overview
In this challenge, we are updating the SDK to expose the new functionality of APIs that are currently being built. We have also split our monolith backend into multiple microservices. So in this challenge, we would need to clean up the calls to the old backend and update it to use multiple endpoints.
This is the third challenge in the series to create the Android SDK, jump in now there will be lots of challenges coming.
Please check concurrent ios challenge here which have same requirement for iOS https://www.topcoder.com/challenges/30119080Project Overview
The project objective is to build an SDK for the Loyalty Payment Card(LPC) for our client. This SDK will be used by LPC’s clients to build the LPC mobile app.
So the SDK will provide all required functionalities from authentication to payment processing, reward management, etc.
The output of this challenge and series will be used by the client to build their Android app. Post this challenge we will be integrating with live versions of these APIs
Assets
-
Swagger files are shared in the forum.
-
Mock versions of the Backend APIs are available.
Technology Stack
-
Android SDK
Individual Requirement
- Follow base SDK code base with best practices
- Implement calls to all the endpoints that were split into microservices.
- It should be working with mock backends that are hosted.
- Clean up of code that references the old monolith backend.
- Add new header to pass api access key
- Header name must be configurable on sdk
- Api access key should be configurable by the app using our sdk
E.g. pass the api access key as “api-access-key” header with value read during sdk initialization. And the name of header “api-access-key” should be configurable on our sdk.
- Unit tests are required and coverage shouldn’t go down
- Clear documentation of code is required. All of the methods need to have clear and robust documentation so that developers using the SDK must find helpful
Final Submission Guidelines
Please submit the following: