03 / Software / 2025
Android property management.
ReCoLA / Android property management
01 / SCOPE
Problem and
scope.
Property management information is scattered across addresses, images and related records. ReCoLA brought these workflows into an Android application with local persistence and map-based navigation.
I implemented the property and maps features using Kotlin, Jetpack Compose, Room and Google Maps. This included creating, viewing, editing and deleting properties, geocoding addresses, sorting by distance, assigning suppliers, storing images and testing the property/map workflows.
02 / IMPLEMENTATION
Implementation
details.
- 01Compose interface
- 02Property workflow
- 03Room storage
- 04Geocoding
- 05Map / list
Property editing and persistence.
Build property creation and editing through Compose state, persistence and navigation, rather than treating the map as a disconnected view.
Location permissions and sorting.
Offer proximity sorting when location is available and a predictable alphabetical fallback when it is not.
Property images and suppliers.
Use internal image files alongside stored property records, with supplier assignment and property/map test cases connecting the workflow.
03 / PROJECT SCOPE
Project scope.
Contribution scope is supported by the project evidence and attributed Git history. Tenant, billing and maintenance features belong to the wider team application.
Context & limitations
This was an academic team application, not a production service. Maps and geocoding need connectivity; “fully offline” would overstate the design. The visual on this page is a schematic using fictional property labels.
Heston pricing and calibration.
Individual dissertation / Heston model