Always-on floating entry
A persistent floating window that stays available across every app and screen.
- Persistent entry point
- Works across any app
- Always within reach
为什么重要
面向快速演示、长期部署和后续更新。
Android AI assistant automation
Multi-step Agent workflows for taps, input, settings, and cross-app actions.
Live captions and translation
Voice and system-audio captions with offline recognition and translation support.
Screen understanding and OCR
OCR, visual parsing, and content analysis for screenshots and camera views.
Multilingual interface
Default English with Japanese, Korean, Chinese, Arabic, and more language options.
SEO-ready publishing
Static pages, localized URLs, sitemap coverage, and structured data for Google indexing.
产品范围
Google 需要理解的产品关键词都放在页面里。
Offline speech recognition
Keep voice workflows usable when the device is offline or the network is unstable.
OCR and translation
Extract text from the screen and translate it into the target language quickly.
Remote configuration
Keep product copy, links, and deployment notes easy to update without code churn.
Static deployment
Fast HTML delivery that is easy to host behind nginx and simple to index.
语言覆盖
默认英语，同时准备了多个可直接发布的语言版本。
语言覆盖
Starry AICore 将 Android 设备变成 AI 工作空间，集成悬浮入口、Agent 自动化、实时字幕、屏幕理解和离线语音识别。
English简体中文日本語한국어EspañolFrançaisDeutschItalianoPortuguêsРусскийTürkçeالعربية
Google SEO 方案
静态 HTML、结构化数据和易爬取 URL 让收录更直接。
Google SEO 方案
Google should index a clean static site with clear product keywords, alternate locale paths, and structured metadata.
- Use a single canonical domain and keep one localized URL per language.
- Ship robots.txt and sitemap.xml so Google can discover every page quickly.
- Add SoftwareApplication and Organization JSON-LD to describe the product clearly.
- Keep titles, meta descriptions, and first-screen copy aligned with the main keywords: Android AI assistant, floating window, live captions, offline speech, screen understanding, and automation.
常见问题
面向用户、支持团队和搜索引擎的简短答案。
What is Starry AICore?
Starry AICore is an Android AI workspace with a floating entry point, agent workflows, live captions, and screen understanding.
Why are there separate language pages?
Separate locale paths improve readability for users and make it easier for Google to index the correct language version.
How should the APK link be updated later?
Edit the APK URL in content.js, rebuild the site, and redeploy the generated dist folder.