Feedback
How to send feedback during the beta.
Applies to Appylar v1.0
During the private beta your feedback shapes Appylar directly. There's no ticket portal to learn and no external tool to sign up for — feedback lives right inside the Developer Portal, and a real person on the team reads every message.
#How feedback works
Open Feedback in the portal, pick a category, add a subject and a message, optionally attach a screenshot, and send. That's it — the message goes straight to the team. You'll see a confirmation, and the form clears so you can send another.
There's no back-and-forth thread inside the portal by design. If we need to follow up, we'll reply to the email address on your account.
#Bug vs. feature — which category?
| Category | Use it for |
|---|---|
| Bug | Something is broken or behaves wrong — an error, a crash, wrong numbers, a creative that won't upload. Include steps to reproduce and a screenshot if you can. |
| Feature request | Something you wish Appylar did — a new capability, an option, a better workflow. |
| Question | You're not sure how something works or whether it's expected. (Check Troubleshooting and the FAQ first — your answer may already be there.) |
| General feedback | Anything else — impressions, rough edges, things you liked. |
One topic per message keeps things easy to act on. Send separate feedback for separate issues rather than one long list.
#What to expect
We triage beta feedback continuously. Because the beta cohort is deliberately small (10–20 studios), we usually get back to anything that needs a reply within a few business days — often sooner for a blocking bug. Not every message needs a reply: feature ideas and general notes are logged and folded into the roadmap.