Skip to content

Android application written in Kotlin, developed as a mobile client for a backend REST API supporting internal retail workflows.

Notifications You must be signed in to change notification settings

asik14014/Accounting

Repository files navigation

FourSeasons Android App

Android application written in Kotlin, designed as a mobile client for a backend accounting and data management REST API.

Status: Legacy / archived project
Purpose: Mobile client application developed for an internal business system supporting retail operations in a boutique network.
Note: This repository does not contain production secrets or credentials.


Overview

This project represents the Android client application of a client–server system, built to interact with a backend REST API.

The application focuses on:

  • presenting data provided by the backend
  • sending user actions and requests via API calls
  • managing UI state and navigation
  • acting as a thin client without embedded business logic

The project demonstrates common Android architectural patterns used in real-world client applications.


System Architecture

┌────────────────────┐
│ Android App │
│ (Kotlin) │
│ │
│ • UI / ViewModel │
│ • API Client │
└─────────▲──────────┘
│ REST / JSON

┌─────────┴──────────┐
│ Backend API │
│ (.NET Web API) │
│ │
│ • Controllers │
│ • Services │
│ • Domain Models │
└─────────▲──────────┘

┌─────────┴──────────┐
│ Database │
│ (SQL Server) │
└────────────────────┘


Key Features

  • Native Android application (Kotlin)
  • Client-side interaction with backend REST APIs
  • Data visualization and basic CRUD workflows
  • Navigation between functional screens
  • Configuration-driven environment setup

Project Structure

Typical Android application structure:

  • ui/
    Activities / Fragments responsible for user interaction and presentation

  • viewmodel/
    ViewModels handling UI state and lifecycle-aware logic

  • network/
    API clients, request/response models, and networking logic

  • model/
    Domain and data models used across the application

  • utils/
    Common helpers and shared utilities


Architecture Highlights

  • Separation of UI and business logic
  • Lifecycle-aware components
  • MVVM-style architectural approach
  • Clear boundary between UI and network layers
  • Designed to work as a client for an external backend service

Technology Stack

  • Language: Kotlin
  • Platform: Android
  • Build System: Gradle
  • Architecture: MVVM-style separation
  • Networking: REST-based API communication

Distribution

The application was previously published on Google Play and used in a production context. The developer account has since been closed due to inactivity.

About

Android application written in Kotlin, developed as a mobile client for a backend REST API supporting internal retail workflows.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages