Creating a Project
Learn how to set up your first project and get personalized tech stack recommendations.
Creating a Project
Learn how to set up your first project and get personalized tech stack recommendations.
Step 1: Start a New Project
- Log in to your StacksFinder account
- Click "New Project" on your dashboard
- Give your project a name (e.g., "E-commerce MVP")
Step 2: Describe Your Project
Project Type
Choose the type of application you're building:
- Web Application — Browser-based apps
- API/Backend — Server-side services
- Mobile App — iOS or Android apps
- Full Stack — Complete applications
Project Scope
Tell us about your ambitions:
- MVP/Prototype — Quick validation, minimal features
- Production App — Full-featured, production-ready
- Enterprise — Large-scale, complex requirements
Step 3: Set Your Priorities
Adjust the priority sliders to tell us what matters most:
| Priority | Description |
|---|---|
| Performance | Speed and responsiveness |
| Scalability | Growth potential |
| Developer Experience | Ease of development |
| Time to Market | Speed of delivery |
| Cost | Budget considerations |
The sliders automatically rebalance — if you increase one priority, others adjust accordingly.
Step 4: Add Constraints
Optional but helpful:
- Team Size — Solo, small team, or large team
- Existing Technologies — Tech your team already knows
- Deployment Target — Cloud, on-premise, or hybrid
- Budget Range — Free, moderate, or unlimited
Step 5: Generate Your Blueprint
Click "Generate Blueprint" and wait while our algorithm:
- Analyzes your requirements
- Scores relevant technologies
- Selects the best matches
- Generates explanations
This usually takes 10-30 seconds.
Tips for Better Results
Be Specific About Goals
Instead of "I want a fast app", try:
- "I need sub-100ms response times"
- "The app should handle 10,000 concurrent users"
Consider Your Team
If you're working alone, prioritize technologies with:
- Good documentation
- Active communities
- Low learning curves
Think Long-Term
A technology that's "good enough" for MVP might not scale. Consider:
- Where will you be in 1 year?
- What features might you add?
- How will your team grow?
Next Steps
- Understanding Scores — Learn what the numbers mean
- Exporting Blueprints — Save your results