Contact person: Business Client

Phone:Show

Email:Show

Location: San Antonio, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"This Android application is an extension of a primary system. (we already have the 4 screens done with Jetpack Compose - Material Design 3) but we need someone that is an expert in jetpack Compose - Material Design 3, for further modifications. We have the SQLite tables and DB done. We have a PPTX with all the info needed... this project is not from scratch, we have everything, we just need someone to make the screens function using Kotlin.

It only receives data from the main application via API endpoints (a document with these endpoints will be provided), stores that data locally in a database (SQLite/Room), then to later send back to the primary system through API endpoints.

When the device is online, the application performs real-time, two-way synchronization:

1. Downloads master records and their details from the primary system.

2. Sends locally generated transactions back to the primary system.

The application must operate fully offline, persisting everything in the local database, allowing all actions without network connectivity, and automatically synchronizing once the connection is restored.

IDE: Android Studio (latest stable)
Language: Kotlin (100% native)
UI: Jetpack Compose + Material 3
minSdk: 30 (Android 11)
target/compileSdk: 34 (Android 14)
Architecture: MVVM + Coroutines/Flow
Dependency Injection: Hilt
Local storage (offline-first): Room (SQLite)
Background sync: WorkManager

Deliverables:

• Source code. In addition to the codebase, you must deliver all necessary, well-organized documentation so the app runs correctly and my in-house team can maintain it without friction:
•
• A README with build/installation instructions.
•
• An architecture summary (layers, modules, and diagrams).
•
• The data model (Room schema and migrations).
•
• The API specification (contracts and examples).
•
• A UI/UX guide (themes, components, and flows).
•
• Code standards (conventions, error handling, DI, MVVM + Coroutines/Flow).
•
• A test plan with evidence of execution.
•
• A release notes document.
•
• Everything must be structured into clear folders within the repository, build cleanly, and be sufficiently documented so developers can understand where everything is, how it’s implemented, and how to extend it." (client-provided description)