Findly Android MVP Prototype
Budget: $250 – $750 USD
I want to build a lean Android MVP for Findly, the app that will spare users from jumping across multiple sites when they need a service or product. At this stage I only need a functional prototype, not a polished production release.
The scope is tight and clear:
• Core flow — a single screen with a search bar feeding a results list.
• User interactions — accept free-text queries, apply basic in-memory filtering, and display a concise detailed view when an item is tapped.
• Data — mock or lightweight local data is fine; the list should surface service details and product listings so I can validate usability.
I care far more about clean, scalable Kotlin (or Java) than fancy visuals. A straightforward MVVM/Repository setup in Android Studio, Jetpack libraries, and sensible naming are what I’ll review first. If Compose accelerates you, great—otherwise classic XML is acceptable.
After an initial chat I’ll share the rest of the technical notes, but the deliverable I’m expecting is:
1. Source code in a private Git repo with clear README instructions.
2. An installable debug APK that shows the search-filter-detail loop working smoothly on Android 8+.
I’m open to continuing as partners if we click, yet a one-off MVP build is perfectly fine too. Consistent, transparent communication is a must—think startup pace with quick iterations, not corporate waterfall. If this sounds like the right kind of challenge, let’s talk details and timelines.
The scope is tight and clear:
• Core flow — a single screen with a search bar feeding a results list.
• User interactions — accept free-text queries, apply basic in-memory filtering, and display a concise detailed view when an item is tapped.
• Data — mock or lightweight local data is fine; the list should surface service details and product listings so I can validate usability.
I care far more about clean, scalable Kotlin (or Java) than fancy visuals. A straightforward MVVM/Repository setup in Android Studio, Jetpack libraries, and sensible naming are what I’ll review first. If Compose accelerates you, great—otherwise classic XML is acceptable.
After an initial chat I’ll share the rest of the technical notes, but the deliverable I’m expecting is:
1. Source code in a private Git repo with clear README instructions.
2. An installable debug APK that shows the search-filter-detail loop working smoothly on Android 8+.
I’m open to continuing as partners if we click, yet a one-off MVP build is perfectly fine too. Consistent, transparent communication is a must—think startup pace with quick iterations, not corporate waterfall. If this sounds like the right kind of challenge, let’s talk details and timelines.