A very simple application made in Kotlin to improve my skills and learn more about this fantastic language. The application uses the Lufthansa Group public API and consists in a form to select origin and destination airports, with some suggestions while is writing, to load those airports in a map and the flights related with them.
The following is a brief description of the technical decisions taken for the development.
This application has three possible error scenarios. The first occurs on the airport data loading screen. Two requests are made, the first is the authentication request to receive the access token. The second error is a check of empty fields before searching for flights. The missing field(s) is(are) marked in red so that the user has feedback and can act accordingly. Third, the request to receive the airports is made. There is a wide range of errors in both requests, so the error message of the server is displayed in the error screen. The user can retry the connection using the retry button. The second error scenario occurs when requesting flight information between origin and destination. Occasionally, the server does not find route data and returns a 404. Therefore, an error suggestion is displayed instead of the flight list.
Used the Lufthansa Open REST API (documentation guides)
https://api.lufthansa.com/v1/
Access to Lufthansa services is controlled via tokens (Oauth 2.0).
POST oauth/token
| POST Parameter | Value |
|---|---|
| client_id | Your client application key |
| client_secret | Your client secret |
| grant_type | "client_credentials" |
List all airports or one specific airport. All airports response is very large. It is possible to request the response in a specific language.
GET references/airports/{airportCode}
Scheduled flights between given airports on a given date.
GET operations/schedules/{origin}/{destination}/{fromDateTime}
- Application written in Kotlin based on Clean Architecture for layer abstractions (view/domain/data)
- Model-View-Presenter for the presentation layer
- Interactors / UseCases are used by the presenters to start a data retrieval flow
- UseCases use Repository pattern to request the data needed
- Repository in this case doesn't have DataSources because there's no database/cache/other sources to retrieve data than just * Network. Repository in this project directly request data to the API
- Two different data objects, DTO (Data transfer object) to parse API's response, and Business Object as our own data model.
- DI with Dagger2
- Asynchronous handled by RxJava2 (RxKotlin)
- Animations provided by Lottie
- RxKotlin https://github.com/ReactiveX/RxKotlin
- Dagger 2 https://google.github.io/dagger/
- Retrofit 2 https://square.github.io/retrofit/
- OkHttp 3 https://github.com/square/okhttp
- Lottie https://airbnb.design/lottie/
- Instrumentation Testing
- Cache / database