Google Cast 平台的使用者體驗
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
透過 Google Cast,Android、iOS 和 Chrome 網頁應用程式可以將影片、音訊和螢幕分享 (鏡像) 等內容「串流播放」到支援 Cast 的裝置,例如:
- Google Chromecast
- 支援 Google Cast 的電視
- 支援 Google Cast 的音箱
- 智慧螢幕 (可攜式觸控 LCD 螢幕,用於做為超薄型電腦)
- Android 平板電腦
在 Google Cast 互動模式中,手機、平板電腦或筆記型電腦是傳送端,可做為遙控器控制播放作業;電視、螢幕或已固定在電腦上的平板電腦則是接收端,可接收傳送端的指示,並顯示透過接收端網際網路連線取得的內容。所有使用者動作 (輕觸和滑動) 都可以在傳送端裝置或 Web Receiver 上執行。
投放功能需要兩個或更多螢幕的協調,也就是發送端 UI 和接收端 UI,兩者必須共同運作。舉例來說,如果您按下行動裝置上的按鈕暫停內容,電視應會顯示內容已暫停,而行動裝置則應提供播放按鈕,讓您繼續播放內容。
注意事項
由於硬體和資源限制,Google Cast 支援應用程式會受到以下限制:
- Chromecast 裝置是低耗電裝置,記憶體、CPU 和 GPU 皆有限制,因此網頁接收器應用程式應盡可能輕量化。
- 對於 Cast 和 Google Cast 互動模式,您可以在 Web Receiver 或傳送端應用程式中建立分頁、視窗或彈出式視窗,並直接接受使用者輸入內容,例如輕觸或滑動。舉例來說,在已插入座架的平板電腦或螢幕上,網路接收器應用程式可顯示暫停按鈕,並接收使用者的輕觸動作。如此一來,應用程式上的「所有」動作都必須從網路接收端或傳送端應用程式觸發。
- 智慧多媒體螢幕支援使用者透過傳送端應用程式或在 UI 上輕觸輸入內容。
- Web Receiver 是針對影片播放最佳化的 Chrome 瀏覽器。因此,WebGL 和 Chrome 原生用戶端 (NaCL) 目前不受支援,Chrome 擴充功能也是如此。
- Cast 支援在
<audio>
和 <video>
標記中播放單一並行的媒體串流,或使用 WebAudio API 播放多個音訊軌。在任何時間點,DOM 中只能有一個影片元素處於活動狀態。此外,系統不支援影片合成、操控、轉換、旋轉或縮放。
整體設計原則
開發使用者介面時,請注意下列事項。
網頁接收器介面:
- Web Receiver 可同時提供互動元素和資訊元素,用來說明應用程式的狀態,例如暫停或播放狀態,或是錯誤訊息。使用者互動可在 Cast 傳送器 (手機、平板電腦或 Chrome 瀏覽器) 或網路接收器 (電視、螢幕或平板電腦) 上進行。
- 請注意,影片動作會在電視螢幕中央執行,您的 UI 元素不應幹擾簡報。將 UI 元素放在 Web Receiver 顯示畫面的三分之一下方,並保留 10% 的邊緣留白,以防超掃。
- 盡可能讓畫面狀態轉換流暢,並營造電影般的感受。為了避免突如其來地從狀態移動,應使用淡入和淡出等轉換效果。舉例來說,內容載入狀態會在畫面上停留,並淡出媒體播放體驗。
寄件者介面:
- 傳送端支援使用者動作,而 Web Receiver 會顯示狀態資訊。舉例來說,如果內容處於暫停狀態,電視應顯示內容處於暫停狀態,而行動裝置則應顯示內容已準備好開始播放 (例如向使用者顯示播放按鈕)。
- 速度是致勝的關鍵。使用者必須能夠快速找到投放控制項,並立即在大型螢幕上看到內容開始播放。在內容載入期間,提供動畫載入指標,並使用轉場效果,讓使用者感覺載入速度更快。
如要確保 Cast 應用程式遵循這些原則,最簡單的方法就是使用 Cast 設計檢查清單檢查使用者介面,並測試 Cast 應用程式。
品牌宣傳指南
以下是 Google Cast 品牌規範,適用對象為應用程式開發人員,主要說明您必須遵守的其他規定,才能在文字中描述應用程式。如需投放裝置品牌宣傳指南,請參閱合作夥伴行銷中心。您可以使用「支援 Google Cast」一詞,讓其他人知道您的應用程式支援 Google Cast。不過,請務必確認您的應用程式符合 Cast SDK 附加開發人員服務條款和設計檢查清單的規定,且使用「Google Cast 支援」時遵守我們的品牌使用規範。
只要應用程式或裝置符合我們的徽章指南,您也可以使用 Google Cast 徽章。如果徽章不符合品牌規範,Google 有權要求您修改或停止使用徽章。
文字中的「Google Cast」
- 描述支援投放功能的應用程式 (而非硬體產品) 時,請使用「支援 Google Cast」這個詞組。例如:「這個應用程式已啟用 Google Cast」。
- 描述與 Cast 相容的第三方硬體產品時,請使用「這部{電視}支援 Google Cast」或「這些{音箱}支援 Google Cast」等字句。
- 在文字中書寫「Google」和「Cast」時,應使用大寫字母。
- 凡是行銷素材在文字或徽章/標誌中使用「Google Cast」時,都必須加上以下法律聲明:Google Cast 是 Google LLC 的商標。
- 請勿在應用程式名稱中加入 Google Cast (例如 XYZ Google Cast 應用程式)。
支援 Google Cast 的應用程式訊息
您可以透過下列方式宣傳應用程式:
- 「XYZ 是支援 Google Cast 的應用程式,可讓你從行動裝置串流播放喜愛的娛樂內容到電視上。」
- 「現在可以在支援 Google Cast 的電視上使用 XYZ 應用程式。」
- 「XYZ 應用程式現已支援所有 Google Cast 產品,包括 Google Chromecast、Google Cast Audio,以及支援 Google Cast 的電視和音箱。」
- 「XYZ 應用程式支援 Google Cast,讓您在電視上透過 Google Cast 盡情觀賞所有最愛的節目/電影/音樂/遊戲。」
- 「XYZ 應用程式現在支援 Google Cast,使用者可以將內容從手機串流至支援 Google Cast 的電視。」
Google Cast 徽章
您可以在網站、應用程式商店資訊、行銷素材和宣傳素材中使用「Google Cast」徽章,顯示與使用 Cast 通訊協定的裝置相容性。
- 請勿修改徽章圖片的顏色、比例、間距或任何其他元素。
- 與其他元素技術 (例如藍牙、Spotify Connect、AirPlay 等) 的標誌一起使用時,Google Cast 徽章的大小必須與其他元素技術標誌相同或更大。
- 請勿將徽章設為網頁上的主要元素。
- 請在網頁上為徽章與其他標誌和圖示保留適當的距離。
- 搭配白色、淺色或中等色調的背景使用時,可以使用黑色徽章。
- 若要在黑色或深色調背景上使用,請使用白色徽章。
- 請勿在含有或顯示成人內容、宣傳賭博、宣揚暴力、含有仇恨言論、涉及向未滿 21 歲者販售菸草或酒精、違反其他適用法律或法規,或有其他不當內容的網頁上使用徽章。
徽章連結
在線上使用 Google Cast 徽章時,必須連結至下列其中一種內容:
- 如要查看 Google 支援 Google Cast 的應用程式和產品清單,請前往 g.co/castapps。
- 您發布的產品清單。
- 你發布的特定產品詳細資料頁面。
- 您發布的應用程式清單。
- 您在 Google Play 或 Apple App Store 上發布的特定應用程式詳細資料頁面。
下載 Google Cast 徽章素材資源
下載套件包含可攜式網路圖形 (.png)、Adobe Illustrator (.ai) 和 Encapsulated Postscript (.eps) 格式。
預覽 Google Cast 徽章
如要瞭解所有可用的徽章和使用說明,請參閱 合作夥伴中心徽章規範頁面。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eGoogle Cast enables streaming of content like video and audio from Android, iOS, and Chrome to compatible devices.\u003c/p\u003e\n"],["\u003cp\u003eThe sender device (phone, tablet, laptop) acts as a remote, while the receiver device (TV, speaker, display) plays the content.\u003c/p\u003e\n"],["\u003cp\u003eBoth sender and receiver UIs must be coordinated for a seamless user experience, with actions reflected on both.\u003c/p\u003e\n"],["\u003cp\u003eWeb Receiver applications should be lightweight due to device limitations, and interactive elements should be strategically placed for optimal viewing.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cast branding guidelines must be followed when promoting app compatibility, including using the approved badge and messaging.\u003c/p\u003e\n"]]],["Google Cast enables content streaming from sender devices (phones, tablets, laptops) to receiver devices (Chromecast, Cast-enabled TVs/speakers/displays). Senders act as remote controls, while receivers display content from their internet connection. Both sender and receiver UIs coordinate actions like pausing/playing. Design considerations include lightweight receiver apps, UI placement within the lower third of the screen, and smooth transitions. Apps can be described as \"Google Cast-enabled\" and use a Google Cast badge, following specific branding guidelines and linking requirements.\n"],null,["# User Experience With the Google Cast Platform\n\nGoogle Cast allows Android, iOS, and Chrome web apps to \"stream\" content ---\nlike video, audio and screen sharing (mirroring) --- to Cast-ready devices\nlike:\n\n- Google Chromecast\n- TVs that work with Google Cast\n- Speakers that work with Google Cast\n- Smart Displays (a portable touchscreen LCD monitor used as a thin client)\n- Android Tablets\n\nIn the Google Cast interaction model, the mobile phone, tablet or laptop is the\n**sender** which acts as a remote control to control the playback, and the TV,\ndisplay or docked tablet is the **receiver** which receives instructions from\nthe sender and displays the content from the receiver's Internet connection. All\nthe user actions (taps and swipes) can take place on **both** the sender device\nor the Web Receiver.\n\nCasting relies on the coordination between two or more screens; the sender UI\nand the receiver UI --- they must work together. For example, if you press a\nbutton on a mobile device to pause the content, the TV should indicate that it\nis paused, while the mobile device should provide a play button to resume\nplayback.\n\nConsiderations\n--------------\n\nDue to hardware and resource limitations, there are certain restrictions placed\non Google Cast-enabled applications:\n\n- The Cast device is a low-power device with memory, CPU and GPU limitations, so the Web Receiver application should be as lightweight as possible.\n- For Cast and Google Cast interaction models, tabs, windows or popups can be created in both the Web Receiver or sender app, as well as directly accept user input, such as taps or swipes. For example, the Web Receiver app on a docked tablet or display can display a pause button and receive a user's tap. In this way, *all* actions on the application must be triggered from either a Web Receiver or sender application.\n- Smart Displays support user input through a sender app or via touch on the UI.\n- The Web Receiver is a Chrome browser optimized for video playback. As such, WebGL and Chrome Native Client (NaCL) are not currently supported, nor are Chrome extensions.\n- Cast supports a single concurrent media stream playback in the `\u003caudio\u003e` and `\u003cvideo\u003e` tags, or multiple audio tracks using the WebAudio API. Only one video element may be active in the DOM at any time. Additionally, video compositing, manipulation, transformations, rotations or zooming are not supported.\n\nOverall design principles\n-------------------------\n\nKeep the following in mind as you develop your user interface.\n\n**Web Receiver interface:**\n\n- The Web Receiver can have both interactive elements and informational elements to describe the state of the app, such as paused or playing, or error messages. User interaction can take place on the Cast sender (phone, tablet, or Chrome browser) or the Web Receiver (TV, displays, or tablets).\n- Remember that the video action is happening in the middle of the TV screen, and your UI elements should not interfere with the presentation. Place UI elements within the lower third of the Web Receiver display, leaving a 10% margin from the edges of the screen for possible [overscan](/cast/docs/caf_receiver/customize_ui#overscan).\n- When possible, transitions from one screen state to another should be smooth and feel cinematic. Rather than abrupt moves from state to state, use transitions like fade-in and fade-out. For example, the content-loading state lingers on-screen and fades into the media playing experience.\n\n**Sender interface:**\n\n- The sender supports user actions and the Web Receiver displays state information. For example, if content is paused, the TV should indicate that it is paused, while the mobile device indicates it is ready to start playing (for example, showing the user a play button).\n- Speed matters. Users need to be able to quickly locate the casting control and see content start playing immediately on the large screen. While content is loading, provide animated loading indicators and use transitions to help make things feel faster.\n\nThe easiest way to ensure that your Cast application follows these principles is\nto review your user interface with the Cast [Design Checklist](/cast/docs/design_checklist)\nand [test your Cast applications](/cast/docs/testing).\n\nBrand guidelines\n----------------\n\nThe following Google Cast brand guidelines are for app developers and focus on\nthe additional requirements you must comply with to describe your app in text.\nFor Cast devices brand guidelines see the\n[Partner Marketing Hub](https://partnermarketinghub.withgoogle.com/brands/google-cast/overview/brand-introduction/).\nYou can let others know that your app works with Google Cast by using\nthe term \"Google Cast-enabled\". However be sure that your app complies\nwith the Cast [SDK Additional Developer Terms of Service](/cast/docs/terms)\nand the [Design Checklist](/cast/docs/design_checklist), and that your\nuse of \"Google Cast-enabled\" complies with our branding guidelines.\n\nYou can similarly use a [Google Cast badge](#google_cast_badge)\nas long as your app or device complies with our badging guidelines. Google\nreserves the right to request that you modify or cease your use of the badge if\nit does not comply with the brand guidelines.\n\n### \"Google Cast\" in text\n\n- When describing an app (not a hardware product) as being Cast-enabled, use the phrase \"Google Cast-enabled\". For example: \"This app is Google Cast-enabled\".\n- When describing a Cast compatible third-party hardware product, use \"This {TV} works with Google Cast\", \"These {speakers} work with Google Cast\".\n- When written in text, \"Google\" and \"Cast\" should be capitalized.\n- In any marketing asset that uses \"Google Cast\" in text or the badge/logo, you must include the following legal attribution: Google Cast is a trademark of Google LLC.\n- Don't put Google Cast in the title of the app (such as XYZ Google Cast App).\n\n### Google Cast-enabled app messaging\n\nYou can promote your app as follows:\n\n- \"XYZ is a Google Cast-enabled app which lets you stream your favorite entertainment from your mobile device to your TV.\"\n- \"The XYZ app is now available for TVs that work with Google Cast.\"\n- \"The XYZ app is now available for all Google Cast products including Google Chromecast, Google Cast Audio, and TVs and speakers that work with Google Cast.\"\n- \"The XYZ app is Google Cast-enabled, allowing you to enjoy all your favorite shows/movies/music/games on your TV that works with Google Cast.\"\n- \"The XYZ app now has Google Cast support, allowing users to stream content from their phone to their TV that works with Google Cast.\"\n\n### Google Cast badge\n\nYou can use the \"Google Cast\" badges on your website, app store listing,\nmarketing materials and promotional materials to display compatibility with\ndevices that use the Cast protocol.\n\n- Don't modify the color, proportions, spacing or any other aspect of the badge image.\n- When used alongside logos for other ingredient technologies (for example, Bluetooth, Spotify Connect, AirPlay, etc.), the Google Cast badge must be of equal or greater size.\n- Don't make the badge the primary element on your page.\n- Keep some distance between the badge and other logos and icons on your page.\n- When used on white, light, or medium-toned background, use a black badge.\n- When used on a black or dark-toned background, use the white badge.\n- Don't use the badge on a page that contains or displays adult content, promotes gambling, promotes violence, contains hate speech, involves the sale of tobacco or alcohol to persons under twenty-one years of age, violates other applicable laws or regulations or is otherwise objectionable.\n\n### Badge linking\n\nWhen used online, the Google Cast badge must link to one of the following:\n\n- Google's list of Google Cast-enabled apps and products at [g.co/castapps](http://g.co/castapps).\n- A list of products published by you.\n- A specific product detail page published by you.\n- A list of apps published by you.\n- A specific app detail page published by you, on Google Play, or in the Apple App Store.\n\n### Download Google Cast badge assets\n\nThe download bundle includes Portable Network Graphics (.png), Adobe\nIllustrator (.ai), and Enapsulated Postscript (.eps) formats.\n\n- [Partner Hub Downloads page](https://partnermarketinghub.withgoogle.com/brands/google-cast/downloads/)\n\n### Preview Google Cast badges\n\nRefer to the [Partner Hub Badges Guidelines page](https://partnermarketinghub.withgoogle.com/brands/google-cast/visual-identity/visual-identity/#badge-guidelines)\nfor all available badges and instructions on usage."]]