https://github.com/karhoo/karhoo-android-sdk
SDK for connecting to the Karhoo System
https://github.com/karhoo/karhoo-android-sdk
cd-deployment cicd ignore-curator team-mobile
Last synced: 6 months ago
JSON representation
SDK for connecting to the Karhoo System
- Host: GitHub
- URL: https://github.com/karhoo/karhoo-android-sdk
- Owner: karhoo
- License: bsd-2-clause
- Created: 2020-04-15T09:05:58.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2024-03-05T09:33:48.000Z (over 2 years ago)
- Last Synced: 2024-03-05T21:40:39.378Z (over 2 years ago)
- Topics: cd-deployment, cicd, ignore-curator, team-mobile
- Language: Kotlin
- Homepage:
- Size: 1.04 MB
- Stars: 7
- Watchers: 19
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# Network SDK
[](https://jitpack.io/#karhoo/karhoo-android-sdk)
Welcome to the Karhoo Network SDK of Android.
#Karhoo Android Network SDK
For more general information about the SDKs, checkout [**the karhoo developer portal**](https://developer.karhoo.com/docs/introduction-to-network-sdk)
## Introduction
The Network SDK provides us with a way of contacting the API of Karhoo and allows us to send and recieve network calls and responses. It is also what provides the Analytics for the App so we know what failures are occuring, how many bookings we have, what requests are succesful and more.
All the quotes, fares, profile information, etc comes through here and is passed on down to the app using it. One of the ways for using this SDK is by following our setup guide found on the Developer site.
This Networking layer is separated from the UI layer in order for consumers of the NSDK to integrate at a faster pace due to there being no need for them to create their own full networking stack.
## Architecture
The base of the Networking SDK is around a service / interactor model. Here we have a single point of entry into the SDK known as KarhooAPI. From here all of the services are accessable with the related interactors.
Each SDK endpoint has its own interactor. These are responsible for fetching data and validating requests which may be null or bad. There is also some examples where the Interactor itself manages the data as is responsible for the mapping of multiple endpoints. A good example of this can be seen in the Quotes Interactor.
