business

Verdict

Submitted 5/24/2026, 3:28:11 PM · Completed 5/24/2026, 3:44:48 PM

6.5
pivot
The idea

My roommates “forgot” to clean again, so I built an app instead of arguing

Show original source text →
Hey everyone🙋‍♂️ I’m a mechatronics student and I’ve been building a small Android app because one thing about shared flats / WGs has been annoying me for a while: Everything is scattered😮‍💨 Money is in one app, groceries in another, cleaning is in a random spreadsheet, repairs get lost in WhatsApp, and after a few months nobody remembers who owns the pan, the kettle, the shelf or whatever is sitting in the hallway. So I started building a roommate / shared-flat app. The idea is not just “another cleaning schedule app”. The main concept is that the apartment itself is the center of the app. Current navigation: Home Apartment Tasks Money Meetup In the apartment section, you create rooms like kitchen, bathroom, hallway, living room, balcony or custom rooms. Private rooms are only shown as resident rooms, but not deeply managed, because I don’t think private rooms should become part of a shared flat management app. Each shared room can then have: inventory / items missing things tasks repairs expenses linked to that room Example kitchen: pan belongs to Gustav kettle belongs to the flat second pan is missing fridge light is broken cleaning supplies were paid by Anna Everything marked as “missing” automatically appears in a “still needed” view, so it is not just another separate shopping list. It is connected to the room and inventory. One feature I added now is a smarter quick-add flow for tasks. If you type something like: “bathroom cleaning Anna” or in German: “Bad putzen Anna” the app recognizes the room, category and person directly: room: bathroom category: cleaning person: Anna The goal is that you don’t have to fill out every field manually. The app detects parts of the input and turns them into chips / suggestions. Tasks can be: open for everyone assigned to one person rotating If a task is assigned to someone, another person can still complete it without the UI turning it into public shaming. So no “Anna failed to do this”, just neutral completion states like “done” or “completed by you”. There is also a small points and badge system, but I tried to avoid making it toxic. No loser board, no public shaming. If someone is clearly ahead in one category, they can hold a badge like: Bathroom Boss Kitchen Hero Trash Wizard Repair Rescuer Shopping Angel WG-MVP Badges only appear if there is a clear lead. If everything is balanced, no badge is shown. Repairs are handled as shared flat problems, not as personal blame: Bathroom — shower head leaking Status: open Note: probably needs a new one, around 15 € Expenses can be linked to rooms, items, repairs or meetups: shower head → bathroom repair shelf → hallway item pasta night → meetup cleaning supplies → kitchen/bathroom There is also a lightweight Meetup section for shared-flat events like cooking together, game night, visitors, balcony night or flat meetings. I added swipe gestures there, so meetup proposals can be quickly accepted, declined or deleted. Design wise I’m going for a clean, beige/off white, calm premium look with cards, whitespace, rounded elements and small animations. Not a cartoonish roommate app. I made a few videos of the current prototype and would love honest feedback: Would you use something like this in a shared flat? Is “everything in one app” actually useful or too much? Does the room-centered structure make sense? Is smart task detection useful or just a gimmick? Which feature sounds most useful? What would you remove immediately? What flatshare problem am I missing? Not trying to advertise it, I want to know whether this problem is real for other people too, or if I just got too annoyed by flatshare chaos.
TRIZ inventive level: 3/5· Principles: segmentation, parameter changes
Synthesis verdict
**Pivot**: The idea of a roommate/shared-flat app centered around apartment management has potential, but it requires a clear monetization strategy and a more focused approach to avoid feature bloat. The room-centric architecture and smart task detection are innovative and useful features, but the market is saturated with specialized tools, and convincing users to switch will be challenging. The app's value proposition hinges on network effects, and platform risk is acute. To succeed, the app needs to differentiate itself from existing solutions, prioritize its features, and develop a sustainable revenue stream.

Strengths

  • Innovative room-centric architecture
  • Smart task detection feature reduces manual input
  • Neutral completion model and limited badge system mitigate toxicity
  • Clear differentiation from existing solutions
  • Strong demand signal from authentic pain-point

Weaknesses

  • Unclear monetization strategy
  • Feature bloat with the inclusion of meetups and badges
  • Market saturation with specialized tools
  • Need for simultaneous group adoption
  • Platform risk and potential compliance changes

Best angle

Focus on developing a robust and user-friendly core feature set, prioritizing room inventory, tasks, and expenses, and explore partnerships with landlords and property management companies for monetization.

Panel verdicts

Viability

meta/llama-4-maverick-17b-128e-instruct

8.0

The app's core concept of organizing shared flat management around the apartment's rooms is innovative and has potential for a useful and user-friendly application.

The idea of a roommate/shared-flat app centered around apartment management is feasible for a solo or 2-person team to build within 4-12 weeks. The core features, such as room inventory, tasks, repairs, and expenses, are well-defined and can be implemented using standard Android app development practices. The smart task detection feature is an interesting addition, but its complexity depends on the Natural Language Processing (NLP) implementation. The design requirements for a clean, premium look are achievable with modern design tools and Android's UI components. However, the scope of the project might be broad for a very small team to complete within the shorter end of the timeframe (4 weeks) if they aim for a polished product. The key features can be developed in a straightforward manner, but the smart task detection and some of the UI/UX elements may require more time and expertise. Overall, with focused development and prioritization, a viable v1 can be built within the given timeframe.

Competition

nvidia/nemotron-3-nano-omni-30b-a3b-reasoning

6.0

A room‑centric, all‑in‑one hub that eliminates context‑switching and keeps shared‑flat assets visible is the core defensible advantage.

The idea tackles a genuine, recurring pain point in shared flats—scattered information about items, tasks, money, and repairs—and proposes a room‑centric hub that unifies inventory, task assignment, expense tracking, and repair notes. Existing solutions are fragmented: Splitwise handles money, OurHome and Cozi manage chores and calendars, while ad‑hoc spreadsheets or WhatsApp groups cover inventory and repairs. This fragmentation creates friction and low adoption, so a single app that links items to specific rooms and automatically surfaces missing items in a ‘still needed’ view offers clear differentiation. The smart quick‑add parsing (e.g., “bathroom cleaning Anna”) reduces manual entry and could become a sticky feature, but its durability depends on accurate natural‑language parsing and consistent usage across all roommates. The neutral completion model and limited badge system mitigate toxicity, addressing a social‑dynamic concern that many flat‑sharing apps ignore. However, the market already contains niche flat‑share platforms (e.g., Flatmates, Roomster) and generic task managers that could incorporate similar features, meaning the competitive moat is modest. Durability will hinge on achieving critical mass, maintaining a clean UI that avoids gimmickry, and continuously adding value (e.g., repair cost estimates, vendor integration). Overall, the differentiation is real but not strongly defensible against larger incumbents that could absorb these features.

Risk

openai/gpt-oss-120b(fallback #1)

4.0

A one‑stop‑shop for flat‑share chores is doomed by market saturation, the need for simultaneous group adoption, and a lack of monetisable users.

The concept tries to be a Swiss‑army‑knife for flat‑share management, but that breadth is its undoing. First, the market is already saturated with specialized tools (Splitwise for money, Todoist/Google Keep for tasks, Trello‑style boards for inventories) and users are unlikely to abandon entrenched habits for a new, unproven app, especially when each existing tool is free and already integrated into their daily workflow. Second, the app’s value proposition hinges on network effects: you need an entire flat to adopt it simultaneously, otherwise the data is fragmented and the app becomes a nuisance. Convincing a group of strangers to switch within a six‑month window is unrealistic, leading to rapid churn once the novelty fades. Third, platform risk is acute: Android’s Play Store policies around data privacy and in‑app purchases could force costly compliance changes, and any breach would instantly kill user trust. Finally, the target audience—students and young renters—have virtually no disposable income, so monetisation via premium features or ads is infeasible, leaving the venture without a sustainable revenue stream. In short, the idea is a feature‑bloat nightmare that cannot achieve critical mass or generate cash before it burns out.

Monetization

mistralai/mistral-nemotron(fallback #1)

7.0

The room-centered approach is a strong differentiator, but a clear monetization strategy is needed to ensure sustainability.

The idea addresses a real pain point in shared living arrangements by centralizing various aspects of flat management into a single app. The room-centered approach is innovative and practical, making it easier to track inventory, tasks, and expenses. The smart task detection feature adds convenience, reducing manual input. The points and badge system, if implemented carefully, could encourage participation without causing toxicity. However, the monetization strategy is unclear. A freemium model with premium features (e.g., advanced analytics, custom badges, or priority support) could work well. The app could also explore partnerships with home goods retailers for affiliate revenue. The unit economics would depend on user acquisition costs and conversion rates to premium tiers. The main challenge will be differentiating this app from existing solutions and convincing users to switch.

Market

moonshotai/kimi-k2.6(fallback #1)

8.0

The room-as-organizing-principle is defensible product strategy, but badges will become shaming tools and 'meetups' dilutes focus; monetize through landlord/property-management partnerships rather than consumer subscription alone.

Strong demand signal from authentic pain-point (scattered flat management across 5+ apps/tools), validated by recurring 'WG' shared-flat culture in Germany/Austria/Switzerland alone (~10M people in target demographic, high willingness-to-pay for harmony). Room-centric architecture is correct insight: physical space > person as organizing principle reduces blame cycles. Smart-parse 'Bad putzen Anna' is genuinely useful (saves 30+ seconds per task, reduces friction enough to change behavior), not gimmick—BUT only if recognition accuracy >90% or it becomes frustrating. Most valuable features: 1) linked expenses-to-items-to-rooms (solves 'who owns kettle' / 'who paid 15€' drift), 2) neutral task rotation without public shaming (critical for retention—flatmate apps die when they become weapons), 3) 'still needed' auto-inventory from natural language. Missing or risky: no clear monetization path beyond 'premium calm design' (B2C flatmates are price-sensitive; B2B landlord/platform integration is stronger); 'Meetup' section is nice-to-have, not need-to-have—swipe gestures here feel like feature bloat that dilutes core utility. Immediate removal candidate: badges entirely ('Bathroom Boss' becomes shaming even with good intent; flat harmony requires perceived fairness over gamification). Smart-add flow should auto-detect room from item context (shower head → bathroom) but MUST allow one-tap correction before chip-lock to avoid misfires. Audience size: DACH region 3-4M shared flats × 2.4 flatmates × 60% smartphone penetration = ~5M potential users; willingness-to-pay €2-4/month or €15-20 one-time is realistic if it prevents one 'who bought the pan' argument. Unmet need is real and undermonetized—competitors (WG-Gesucht, Splitwise, Trello, WhatsApp groups) each solve 20% but integrate poorly. Verdict: build core (tasks+expenses+inventory with room-linking) ruthlessly, defer meetups and badges, test smart-parse accuracy with 50 real flat inputs before shipping.

Synthesized by meta/llama-3.3-70b-instruct · 21.4s