HugeOne
iOS/Android app for investors to discover startups. MVP specs - a living document, updated as we work through the Figma design.
Overview
HugeOne connects potential investors with startups raising funds. On the MVP, no real investment is possible: the app is for discovery only. Investors browse startups, review their KPIs, documents and news, and shortlist the ones they're interested in, ahead of a funding flow that opens in V1.
| Platforms | iOS + Android |
|---|---|
| Mobile stack | Flutter (single codebase) |
| MVP scope | Discovery only, no investment, no payment |
| Design source | Figma, file "HUGE ONE", canvas "MVP launch" (~65 screens) |
Clickable prototype
The golden path (feed, swipe, startup profile, favorites) as clickable HTML screens, wired with mock data and real navigation, not just static pictures. Reuses the design system's actual CSS, so what you click through is already built with the same components a developer would use.
Covers: Feed with swipe left/right, tap a card to open its profile (Overview tab), add to favorites, empty states for both the feed and favorites. The other five profile tabs and the auth flow aren't built yet, next pass.
Target users
Potential investor
Someone looking to identify promising startups before deciding to invest (in V1). On the MVP, they browse, compare, and shortlist. No financial KYC yet, just a secured account.
Startup (content side)
Has no account of its own on the MVP. Its profile (KPIs, documents, news, team) is fed by the HugeOne internal team through the back office. No startup self-service at this stage.
Authentication MVP: simple
No financial KYC and no crypto wallet on the MVP (the Figma flow includes wallet/sepolia steps, kept in reserve for V1, see roadmap).
Later sign-in: passcode or biometrics directly, no need to go through email again.
Feed & swipe (discovery)
Tinder-style mechanic: each startup shows as a card, and the investor swipes to decide.
| Action | Result |
|---|---|
| Swipe right | Startup added to Favorites, removed from the current feed |
| Swipe left | Startup passed, removed from the current feed, can come back later (see below) |
| Tap the card | Opens the startup's detailed profile |
Feed states to cover: loading (skeleton), empty feed (no more startups to show), network error.
Kpi.date or News.published_at is more recent than Swipe.date.Favorites
List of startups swiped right. Works as a shortlist for closer review before V1, where an investment action becomes possible from this list.
Empty state to design: no favorites yet, prompt to go back to the feed.
Startup profile
Detailed screen reached from the feed or favorites. Based on the Figma structure ("Business profile"), organized into tabs:
| Tab | Content |
|---|---|
| Overview | Startup summary, pitch, sector, funding stage (pre-seed / seed / series A / B+) |
| KPIs | Minimal set from the Figma mockups: number of investors, amount raised / funding goal, rating or score |
| Documents (V1 Document / Wall) | Files uploaded by the startup through the back office (pitch deck, reports...), read-only for investors |
| Team | Founders and key team members |
| Feed | News the startup publishes about its progress |
| Q&A | Investors can submit a question; the internal team answers it through the back office, then it's published for every investor to read |
Data model (first pass)
To refine with the developer, this is a starting point based on the flows above.
| Entity | Key fields |
|---|---|
Investor | id, email, passcode_hash, biometric_enabled, created_at |
Startup | id, name, pitch, sector, funding_stage, publication_status |
Kpi | id, startup_id, label, value, date |
Document | id, startup_id, type, url, uploaded_by (admin), date |
News | id, startup_id, title, content, published_at |
TeamMember | id, startup_id, name, role, photo |
Swipe | id, investor_id, startup_id, direction (right/left), date |
Favorite | investor_id, startup_id, added_at (derivable from a right swipe) |
Question | id, startup_id, investor_id, question_text, asked_at, answer_text, answered_by (admin), answered_at, status (pending/published) |
Screen inventory (Figma)
About 65 mobile-sized frames found on the "MVP launch" canvas, spread across these sections:
- Feed (plus loading and empty states)
- Favourite (plus empty state)
- Registration (5 steps), Open app, Log in
- Business profile (Overview, KPIs, Documents, Team, Feed, Q&A)
- Investment Flow V1, out of MVP scope
Design system
Not extracted automatically yet (reading Figma variables needs the desktop app with an active selection, which isn't available over remote access). To do in a session with Figma desktop open, or by documenting manually: colors, typography, spacing, and components (primary/secondary buttons, cards, tab bar, navigation) already visible in the file.
Admin back office
Internal interface (HugeOne team, not the startups) to:
- Create and edit a startup profile (info, funding stage)
- Upload and manage KPIs
- Upload documents (pitch deck, reports)
- Publish news on the startup's behalf
- Manage publication status (draft / published / unpublished)
- Answer pending investor questions and publish them to the Q&A tab
No startup account on the MVP, everything goes through the internal team. To spec in detail in a later pass (screens not yet designed in Figma).
Out of scope for MVP
- Any real investment flow (payment, amount, confirmation)
- Financial KYC for investors
- Crypto wallet / blockchain connection
- Startup self-service account
V1 roadmap future
- Investment Flow: amount, confirmation, tracking an investment (already sketched in Figma)
- Investor KYC (identity verification before a real investment)
- Crypto wallet / sepolia step (already present in the Figma sign-up flow, disabled for MVP)
- Possible startup self-service account (open question: keep internal curation or open it up?)
Decisions made & open questions
Decisions
- Mobile stack: Flutter
- Repo holds specs only, no app scaffold
- Simple MVP auth, no KYC or wallet
- Swipe right = favorite, swipe left = pass, but a pass is reversible: the startup returns to the feed once it posts a new KPI or news update
- Back office: internal team only
- Q&A: investors can ask a question, the internal team answers and publishes it (not a live chat)
- KPIs shown: number of investors, amount raised / funding goal, rating or score (the minimal set already in the Figma mockups)
- Figma screen cleanup (duplicates, naming) happens after the clickable prototype, not before