Create project structure
Feature-first folders, clear module boundaries, and naming that matches how the app actually grows—so onboarding a teammate or splitting a package does not start with archaeology.
Yogesh Sharma
Available for Flutter & mobile product work
Hi, I’m Yogesh Sharma
Flutter developer with hands-on experience building and shipping cross-platform mobile apps for iOS and Android. I work with Dart, Firebase, Bloc, Riverpod, and REST APIs to create fast, well-structured apps — from the first screen to a live store release. Most of my recent work is in sports and venue booking, where high traffic and real-time availability make the technical details matter.
What I build
Empty slots
become busy courts.
I build Flutter apps the way I want to inherit them: a clear project structure so every feature has a place, clean architecture so business logic is not trapped in widgets, and a deployment process so Play and App Store releases are boring in the right way. A lot of my public work is court and venue booking—fast flows, offline edge cases, and backends that behave when everyone taps “book” at once—but the same habits apply to whatever ships next.
Clean architecture
Presentation, domain, and data stay honest to each other: contracts for APIs and repositories, testable use cases, and state where it belongs—Riverpod or Bloc without turning the UI into a junk drawer.
Deployment process
Build flavors, signing, store listings, and repeatable release steps—so shipping to Play and the App Store is a checklist, not a scramble when the client says “we go live Friday.”
Stack & practices
Tools and patterns I use to ship maintainable apps.
Flutter
Dart
Firebase
Clean Architecture
Riverpod
Bloc
REST / APIs
State management
CI-friendly builds
Material & custom UI
Animations
App Store & Play releases
Problems & how I approached them
Constraints and trade-offs usually matter as much as stack keywords. The cards below summarize recurring problems from high-traffic booking products (without naming confidential clients). Open-source repos in the next section spell out challenges at the code level.
Open source on GitHub
Public Flutter samples: architecture patterns, state management, and product-style demos. Each card summarizes a concrete challenge and what changed in the codebase. Explore the code on github.com/yogeshsha.
Selected work
Live sports and booking apps on Google Play and the App Store. A few highlights include what broke in production or pre-release and how it was addressed. Tap a badge to open the listing. Book and Go Admin / tournament variants are omitted.
Padel, pickleball & sports
Additional projects are not listed here. Besides the public apps above, I have worked on more mobile products that stay off this page because of client confidentiality, NDAs, and white-label agreements. If you are hiring or scoping a build, I can speak to that experience at a high level without naming protected work — get in touch below.