Marketing Guide

Write marketing copy that survives inspection

Good EdgeORE marketing explains why the product is useful, invites a clear next action and makes its current boundaries easy to understand. It does not need a fabricated score, earning estimate or finished-build certification. A judge or customer should be able to move from the homepage to the native preview, source, qualification ledger and handbook without guessing which surface contains sample data.

Lead with the user decision

The core message is private AI on a configured host, guarded Solana actions and portable receipt contents. Keep the brand tagline Your Edge. Your AI. Your Proof., then explain those words concretely. The first call to action can open the hosted Android preview, while a nearby link opens documentation. The concept phone remains useful for showing the intended workspace if Sample data stays visible on every destination.

Use one primary action per section. Do not place five equal buttons at the end of every paragraph. Visitors evaluating trust want source and evidence; visitors learning implementation want the handbook; visitors inspecting interaction want the preview. Clear paths are more persuasive than an endless feature grid. The status panel should be legible on a phone without horizontal scrolling or tiny type.

Use precise capability labels

Current source, runtime qualified, attempted, experimental and planned are different categories. The owned-host AI path belongs to current source with a live-runtime boundary. LiteRT-LM belongs to a separate experimental branch until qualified. Customer-funded SOL contribution belongs to a roadmap, not a reward card. Receipts verify protected contents rather than every descriptive field. These labels make the project easier to assess and prevent downstream decks from repeating overclaims.

Do not say all rights are open source without inspecting the repository license. Do not imply affiliation with Google, Solana Mobile or an upstream node project merely because their libraries are used. Credits belong in developer and notice pages. A distinctive product voice can coexist with careful provenance. The builder can be credited for the integration without claiming authorship of upstream code.

Design an evidence desk

The qualification page should show artifact identity, historical automated gates, hosted launch context and open runtime checks. Link the relevant repository records rather than decorating the page with unverifiable seals. Avoid presenting a timestamped session as an ongoing uptime promise. A full APK hash can be displayed in a wrapping monospace block with an accessible copy control, not abbreviated beyond usefulness.

Screenshots should be classified as concept renders, automated screenshot tests, hosted emulator captures or physical-device captures. A cropped marketing image can be attractive, but link the uncropped evidence where an operational claim depends on it. Video captions must not imply a wallet journey that never completed. An honest partial demonstration is stronger than an edited illusion of end-to-end success.

Review each public surface

Check homepage, footer, AI, storage, nodes, receipts, security, developers, qualification and llms.txt together. One stale sentence can undermine a corrected hero. Search for mining, guaranteed rewards, on-device and complete to ensure they appear only in accurately scoped contexts. The content gate is a consistent story with inspectable evidence and meaningful next actions. The desired quality bar is high; a self-awarded ten-out-of-ten badge is not part of it.

---

Wiki home · Qualification updates · Sources and credits