How novumlogic/android-offline-first-supabase-library works
Project Type and Purpose
• This is an Android “offline-first” library module (SupabaseOfflineSupport) plus a sample Todo application (sample).
• The library provides generic synchronization between a local Room database and remote Supabase tables.
• The sample app demonstrates usage in a full-stack mobile MVVM architecture: UI → ViewModel → Repository → Data Sources → Sync Layer → Supabase.
File Structure Analysis
• Top level:
• SupabaseOfflineSupport/ – Kotlin library module with source under src/main/java/com/example/supabaseofflinesupport.
• sample/ – Android application module implementing a Todo MVVM app under src/main/java/com/novumlogic/todo.
• Gradle configs (build.gradle, settings.gradle, wrappers).
• Library module contains:
• Core sync abstractions: BaseDataSyncer, SyncManager, BaseSyncableEntity, BaseRemoteEntity, GenericDao.
• Helpers: NetworkHelper, RetrofitClient, SupabaseApiService, converters and extensions.
• Sample app module contains:
• Presentation: Activities/Fragments (MainActivity, NewTaskFragment), ViewModels, adapters.
• Data layer: TaskRepository, local datasources/DAOs/entities, remote datasources (TaskRemoteDataSource, CategoryRemoteDataSource), DTOs.
• Room database schema (TodoDatabase) and entity/DAO packages.
• Resources: layouts, drawables, menus, XML, values.
Key Insights from README
• Architecture: MVVM + Repository + Data Source layers + Sync Manager.
• Sync algorithm overview: last-write-wins conflict resolution, two-way merge, timestamp-based.
• Technical stack: Kotlin, Room, Supabase Kotlin client, Kotlinx Serialization.