ELE Store — EV Parts & Batteries Mobile App Designed and developed ELE Store, a client Android ap...ELE Store — EV Parts & Batteries Mobile App Designed and developed ELE Store, a client Android ap...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
ELE Store — EV Parts & Batteries Mobile App
Designed and developed ELE Store, a client Android application for an electric-vehicle batteries and vehicle-parts marketplace. The goal was a clean, modern shopping experience that feels premium and easy to use—similar to high-end retail apps—while staying focused on EV-specific products like lithium battery packs, chargers, motors, brake kits, and charging cables.
The product UI/UX was first prototyped in Figma with a full screen flow: onboarding, home discovery, category browsing, search & filters, product details with variants (voltage/capacity), cart, checkout, favorites, profile, and notifications. The visual system uses a deep forest-green brand palette, electric accent highlights, rounded product cards, and a floating bottom navigation bar for a polished native feel.
Built in Android Studio with Kotlin, following Material Design patterns and a modular screen architecture. Implementation included Jetpack Navigation for multi-screen flows, ViewModel + StateFlow for cart and favorites state, RecyclerView/Compose-friendly product grids, and local mock data (no live backend) so the client could review a fully interactive UI build. Additional Android stack elements: XML/Compose layouts, Glide/Coil-ready image placeholders, and responsive mobile layouts optimized for modern handsets.
Deliverables: production-ready UI screens, clickable navigation, add-to-cart / wishlist interactions, promo-code checkout flow, and a client-ready Android prototype suitable for investor demos and further API integration.
Post image
Post image
Post image
Saad's avatar
Mock data now, real API later is the right call for an investor-ready prototype, speed matters more than correctness at that stage. The part worth locking early is the StateFlow contract shape, if the mock repository returns the same fields and error states the real endpoint...
Muhammad 's avatar
Thanks, I completely agree. For the investor-ready prototype, keeping the data layer mocked will help us move faster while maintaining a production-ready architecture. I’ll make sure the mock repository follows the same response models, StateFlow contracts, loading states, and...
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started