What happens during the analysis
VibeScale examines the code, structure, and metadata of the repository to infer your product’s profile. While the analysis runs, the dashboard shows “Analyzing your app…” — this is normal and usually takes a few minutes. You don’t need to do anything at this point. You can leave the page open or come back later — the result is saved on the dashboard.What is displayed after Discovery
When the analysis finishes, the dashboard shows a set of automatically inferred fields:App Category
The market segment your app fits into (e.g., productivity, fintech, health).
Target Audience
Who the app was built for — user profile or customer segment.
Problem Solved
The main pain point the app addresses, identified from the code and product structure.
Differentiator
What makes your app stand out from existing alternatives.
Wow Moment
The moment when the user first realizes the real value of the product.
Use Case
The concrete scenario where the app is used and delivers the most value.
Main Feature
The central feature that supports the app’s value proposition.
Competitors
Products or alternative solutions competing in the same market space.
- Detected Features — tags with features identified in the repository
- Confidence Score — a bar indicating how solid the inferences are, based on repository completeness and clarity
- Tech Stack — detected languages, frameworks, and tools
- Routes and Endpoints — mapping of routes or endpoints found in the code
Data sources: web research vs. AI inference
Some fields, especially Competitors, indicate the source of the information:
- via web research — data obtained through active search in external sources
- via AI inference — data deduced from the code and repository structure
What to do if the analysis takes too long
The dashboard shows 'Still processing...'
The dashboard shows 'Still processing...'
Larger repositories or those with more complex structures may take longer to analyze. Please wait a few minutes and reload the page — the result is saved automatically as soon as the analysis finishes.
The status remains 'In Progress' for a long time
The status remains 'In Progress' for a long time
If after 10 minutes the status is still In Progress, check if the connected repository is accessible and contains significant code. Contact support if the problem persists.
The status changed to 'Failed'
The status changed to 'Failed'
Click Run again on the dashboard to restart Discovery. If the error continues, contact support with the repository name and the time of the attempt.