Macro Handler

Macro Handler

Android Automation Platform

Community Forum

Community space for macro development, questions and sharing.

Community screens

Forum copy matches the real in-app sharing flows

Forum, public macros, and blocked-user management run on the same community safety layer. The English screens below show how those flows appear in the 1.0.17 app.

Forum: topics, sharing, and safety flow

The clean screenshot shows first-time users where to create a new topic, find the topic list, use filter/search flow, and reach safety actions.

Clean forum screen
1New topicThe New Topic entry starts the title, body, category, publication duration, and safe submit flow.
2TopicsMacro questions, sample scenarios, and announcements are read from this main list.
3FiltersCategory, search, and status filters move the user to the right discussion quickly.
4SafetyReporting, blocking, and moderation areas protect community safety.

Public macros learning map

The clean screenshot teaches where to discover shared macros, check trust signals, and find report/block actions.

Clean public macros screen
1DiscoverShared macros are reviewed with category, intent, and description context.
2TrustOwner, description, badge, and trust signals are checked before running.
3ActionReport, block, and download/run actions support a safer usage decision.

Block Management

Blocked users screen

Macro sharing learning map

The clean screenshot teaches where cover image, selected macro, category, development mode, and publication duration are configured while sharing a macro.

Clean macro sharing form
1PackageCover image, selected macro, and guide editing entry define the core identity of the shared package.
2CategoryCategory selection helps the macro appear in the right context across forum and public macro listings.
3SafetyDevelopment mode and duration clarify whether the source is code editor or no-code workspace and how long the share stays published.

Sharing checklist

What should users check before publishing a macro?

  • Macro selection: Check the selected macro name and guide description so the wrong macro is not shared.
  • Development mode: Code editor and no-code workspace sources create different user expectations; the share description should state this clearly.
  • Publication duration: For trial macros, using a day limit instead of indefinite publishing reduces moderation and maintenance load.
  • Community safety: Macros containing personal data, sensitive coordinates, tokens, or harmful behavior should be cleaned before publishing.

Sign in to participate

Forum access requires a signed-in Google session so community profiles are not exposed to anonymous scraping. Sign in to view topics, reply, or create a topic.