feat(mobile): init SQLite for offline-first support #124
+117
−29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
issue: #123
Description
This PR initializes SQLite for the mobile app to support an offline-first architecture.
On first app launch, a local SQLite database (blob.db) is created and initialized.
A reusable database access layer is added so the connection can be safely used across the app without re-initialization.
The setup is intentionally minimal and focused only on initialization, as required by the issue.
Key points:
• Database is created on first launch
• Initialization is safe to call multiple times
• Uses Expo SDK 54–compatible async SQLite API
• Includes a placeholder schema for future expansion
This lays the groundwork for offline data storage without introducing any business logic or sync behavior.
Dependency changes (if applicable)
Added:
expo-sqlite — for local SQLite support on Expo (SDK 54 compatible)
Summary
This PR initializes SQLite for the mobile app to support an offline-first architecture.
What was done
expo-sqlite(SDK 54 compatible)blob.db)metatable for future useNotes
openDatabaseAsync) required by Expo SDK 54Checklist
Screenshots