Android Offline Data Caching Implementation
Budget: £250 – £750 GBP
I have a fully functional Android app, but it currently depends base44 backend for all functionality ,media, game asset (basic 2d) . I need a robust offline-first layer so users can keep using the app even with zero connectivity. The finished android app is just a launcher for apps hosted on base44 ai.
What needs to be cached
• API responses: every endpoint the app already calls should be persisted locally and served instantly on subsequent requests.
• Media files (images and videos): once an item is viewed or explicitly downloaded, keep it on the device so it opens offline without re-fetching.
Synchronization logic
The moment the user relaunches the app with a connection, the cache must refresh automatically—no background polling required. Each launch should:
1. Check for updated or new API payloads and invalidate/merge them cleanly.
2. Verify media files, downloading only what has changed or is missing to avoid extra bandwidth.
Technical expectations
– Integrate seamlessly with the existing codebase (Java).
interceptors for network caching, WorkManager for the launch-time sync task, and Glide/Picasso for disk-bound image/video handling—whatever combination meets best-practice guidelines.
Deliverables
1. Updated project source with the caching layer fully wired.
2. A concise README explaining the architecture, key classes, and how to tweak sync intervals or cache size.
3. Brief hand-off call or screencast demonstrating offline behaviour, followed by a successful online sync on app open.
If this matches your expertise, let’s get started right away.
What needs to be cached
• API responses: every endpoint the app already calls should be persisted locally and served instantly on subsequent requests.
• Media files (images and videos): once an item is viewed or explicitly downloaded, keep it on the device so it opens offline without re-fetching.
Synchronization logic
The moment the user relaunches the app with a connection, the cache must refresh automatically—no background polling required. Each launch should:
1. Check for updated or new API payloads and invalidate/merge them cleanly.
2. Verify media files, downloading only what has changed or is missing to avoid extra bandwidth.
Technical expectations
– Integrate seamlessly with the existing codebase (Java).
interceptors for network caching, WorkManager for the launch-time sync task, and Glide/Picasso for disk-bound image/video handling—whatever combination meets best-practice guidelines.
Deliverables
1. Updated project source with the caching layer fully wired.
2. A concise README explaining the architecture, key classes, and how to tweak sync intervals or cache size.
3. Brief hand-off call or screencast demonstrating offline behaviour, followed by a successful online sync on app open.
If this matches your expertise, let’s get started right away.