FAQ

Questions builders and early users usually ask.

Quick answers about publishing projects, leaving suggestions, moderation, reports, analytics, and the expert path in the Heyviber public beta.

Open beta

Anyone can browse public projects. Publishing and suggestions require sign-in.

Builders can classify suggestions as accepted, implemented, or won't fix, and hide low-quality feedback.

Reports go to a lightweight admin review list during the first beta phase.

Publish AI-built apps or prototypes you own or are clearly allowed to represent. The project should be real enough for others to review.

Yes. In the public beta, published projects are public immediately. Owners can manage incoming suggestions after publishing.

Not yet. The beta uses a screenshot URL field so the core publishing and feedback loop can stay simple.

Signed-in users can leave structured improvement suggestions on public projects.

Owners can hide inappropriate, duplicate, abusive, or very low-quality suggestions from public view.

Report spam, harassment, scams, impersonation, security abuse, or illegal content. Disagreement alone is not a report reason.

The beta keeps hire requests as a lightweight concierge path. Janne can manually handle early requests while the feedback loop is validated.

Developer verification is manual at first. GitHub is required, LinkedIn is optional, and public reputation features come later.

Heyviber tracks the basic visitor, signup, publish, suggestion, and upvote funnel so the beta can be improved with real usage data.