Cross-platform music player with native platform channels, SQLite favorites, and lyrics display
13 weeks
5
Production
Key Challenge
Reliable native platform channel communication for audio control with graceful web fallback
Skills Demonstrated
Built a Flutter music player featuring native platform service integration, SQLite-backed favorites, song detail screens with lyrics, and a polished splash-to-player transition.
Learning native-mobile integration patterns beyond basic Flutter widgets
Platform channels for audio + SQLite repository for persistent favorites
Polished music player with 5 screens and cross-platform support
5
App screens
2
Target platforms
5
Screens
2+
Platforms
SQLite
Favorites storage
Main player screen
Functional cross-platform music player demonstrating native integration.
Solid foundation for mobile development portfolio.
5
Screens built
System architecture overview
Standard Flutter architecture with screens, widgets, controllers, repositories, services, and models.
MusicServiceBridge wraps native platform channels for audio. FavoritesController uses repository pattern with SQLiteFavoritesRepository for persistence.
Web platform uses sqflite_common_ffi_web as database factory fallback.
Infrastructure & Deployment
Builds for Android, iOS, and web. No backend server required.
Native platform channel audio control.
SQLite-persisted favorite songs.
Song detail screen with lyrics box.
Animated transition from splash to player.
The Problem
Native audio service must initialize before UI renders player controls.
How I Solved It
await MusicServiceBridge.initialize() in main() before runApp().
Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
await MusicServiceBridge.initialize();
runApp(const MyApp());
}The Problem
sqflite doesn't work on web out of the box.
How I Solved It
Conditional import setting databaseFactory = databaseFactoryFfiWeb when kIsWeb.
if (kIsWeb) {
databaseFactory = databaseFactoryFfiWeb;
}The Problem
Toggling favorites on one screen didn't update other screens.
How I Solved It
FavoritesController with ChangeNotifier shared via Provider at app root.
class FavoritesController extends ChangeNotifier {
Future<void> toggle(Song song) async {
await _repo.toggle(song.id);
notifyListeners();
}
}Repository pattern simplifies testing
InMemoryFavoritesRepository let me test UI without SQLite setup.
Platform channels need error handling
Native service calls can fail silently—always wrap in try/catch with user feedback.
Web SQLite needs FFI
sqflite_common_ffi_web is required for SQLite on Flutter web targets.
What I'd Do Differently
Add a proper state management solution (Riverpod/Bloc) instead of setState for favorites.
Healthcare pharmacy platform with patient/pharmacy accounts, prescriptions, orders, and product catalog.
Full-stack meeting room management for Al Baraka with NestJS backend and Next.js dashboard.
Interested in a project like this or want to collaborate on your own?