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.
My supported contribution covers property CRUD, Google Maps/geocoding, proximity sorting, supplier assignment, internal image handling and related tests.
02 / IMPLEMENTATION
Implementation
details.
- 01Compose interface
- 02Property workflow
- 03Room storage
- 04Geocoding
- 05Map / list
Connect the feature across layers.
Build property creation and editing through Compose state, persistence and navigation, rather than treating the map as a disconnected view.
Define behavior when location is missing.
Offer proximity sorting when location is available and a predictable alphabetical fallback when it is not.
Store images with property records.
Use internal image files alongside stored property records, with supplier assignment and property/map test cases connecting the workflow.
03 / RESULTS
Results.
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.
04 / SUMMARY
The property workflow depends on permissions, persistence, location data and failure handling across the application.
Heston pricing and calibration.
Individual dissertation / Heston model