Logs & analytics
Your app misbehaving after launch? Logs are its health report; want to know if anyone's using it? Look at the analytics.
Two dashboards
| Tab | What it shows | When to use it |
|---|---|---|
| Logs | The app's runtime console output and error stacks |
When pages error or APIs don't respond, look for clues here first |
| Analytics | Real visits to the gallery / public share page, plus source and device breakdown | To see if anyone's using it and where they come from |
How to use logs
- Open "More → Logs";
- Find the red error — the last line of the stack usually states the cause;
- Copy the whole block, send it to the AI and say "there's this error in the logs, help me fix it".
This is far more effective than saying "the page is broken" — the AI can pinpoint the exact file from the stack.
How to read analytics
- It counts visits to the gallery / public share page; numbers only appear after the app is deployed on the platform and gets traffic, so 0 right after launch is normal;
- The source breakdown shows where traffic comes from (e.g. how many people a post on X brought in);
- The device breakdown tells you whether to optimize for mobile or desktop first.