PROBLEM_ANALYSIS

Category: 04. No-Code / Low-Code
Section: Phase 1: Problem Definition

1. PROBLEM_ANALYSIS.md

Purpose: To deeply understand the problem without any coding bias, focusing on what can be built visually and rapidly.

I am participating in a no-code/low-code hackathon (using tools like Bubble, Glide, Airtable, or FlutterFlow) and I am a beginner.

Analyze the following problem statement deeply.
[PASTE PROBLEM STATEMENT]

Explain it in very simple language.
Then provide:
1. The actual problem being solved
2. Target users
3. User pain points
4. Existing ways people might solve this problem
5. Limitations of existing solutions
6. Proposed no-code solution ideas
7. Core features
8. Nice-to-have features
9. What should NOT be built during a short hackathon
10. What could make this solution unique
11. A realistic MVP that can be built during a hackathon
12. Potential no-code platforms that could be used (Bubble, Glide, Airtable, FlutterFlow, Softr, etc.)

Do not assume I am an experienced developer.
Explain no-code concepts (workflows, databases, repeating groups) in beginner-friendly language.
Do not suggest custom code unless absolutely necessary.