Building the account flows a team can build on
Socialdeck is a senior-design team project centered on player profiles, decks, games, and social connections. My contribution focuses on an earlier part of that experience: helping a person create an account, complete onboarding, and establish the profile the rest of the app will use.
Connecting a screen to stored data
A sign-up or profile screen needs more than a successful database write. It has to validate input, show that work is in progress, explain failures, and carry the right state into the next screen. My backend integration work connects those flows to the Flutter interface and Firebase services.
Making the boundaries useful to teammates
The shared architecture separates presentation screens, Riverpod state, domain contracts, and Firebase repositories. I work within those boundaries so a widget does not need to know the details of database access and a repository can be reused by another flow.
That separation matters as the team develops friend discovery, requests, and inbox updates. Existing account and profile flows provide a pattern for validation and loading/error/success states, giving later features a consistent foundation.
Progress within a shared project
The account, onboarding, and profile integration described here is my contribution within the team’s application. Broader social functionality remains in progress, and this portfolio does not present the entire product as individual work or offer unfinished features as a live demo.
The lesson for me is practical: a contribution has to make sense to the next person working on it. Clear responsibilities, code reviews, and documentation help teammates connect their work and keep the application coherent as it grows.