Some features are only available on particular plans or as paid add-ons and you can check inclusions on our pricing page. If you have any other questions, contact support and we can review your plan and provide you with options, including to speak to one of our Customer Success team.
Learn the key differences between iOS and Android RCS features, including text, links, rich cards, carousels, and replies. Find best practices to ensure a consistent experience across devices.
There are important differences in how RCS features look and work on each platform. The table below breaks down the key differences and provides best practices to ensure your campaigns display consistently across devices.
iOS vs Android comparison table
| Feature | iOS (18.4+) | Android | Best practice |
|---|---|---|---|
| Basic text messages | Supported, up to 160 characters. Reliable for simple updates. | Supported, up to 160 characters. Reliable for simple updates. | Keep messages short and under 160 characters for readability. |
| Hyperlinks |
Only one per message. If followed by text, may appear unclickable. When placed at the end, shown as a link preview requiring an extra tap. Without an Note: If a link is included in a rich card description, it won’t be clickable. The recommended approach is to place the link in a URL button instead. This applies to both iOS and Android. |
One preview per message. Multiple links show as clickable text. | Place hyperlink last. Add og:image for a cleaner preview. Avoid multiple links. |
| Rich cards | Media may crop. Long text truncated. In iOS 18.5.2, tapping opens full text only (no media/actions). Media cannot be downloaded. | More consistent rendering. Media remains clickable. | Use tall 3:2 media with a 16:9 “safe area.” Keep title/description within three lines. |
| Carousels | Media may crop with large text. Long text truncated. Expanded view shows text only. | Reliable but vertical cropping possible with long text. | Use medium-width carousels with concise text. Avoid chip lists. |
| Suggested replies & actions | Replies display as a permanent list. Actions embedded in the card. Chip lists become menus. | Replies appear as temporary chips that disappear after selection. Actions shown as buttons. | Limit replies to three. Prefer embedded actions over chip lists. |
| Known limitations | Media cannot be expanded. Text truncation more common. Suggested replies persist. | Chips must appear last to render properly. Less truncation overall. | Always test on both iOS and Android. Use SMS fallback for unsupported devices. |
Checklist for consistent design
Keep text under 160 characters or three lines per element.
For rich cards, use 60 characters for title and 160 characters description
Place hyperlinks last and add
og:imagefor clean previews. In text messages, make sure there is a space between your text and a hyperlink otherwise it may only be shown as an unclickable link.Use tall media ratios (3:2 with 16:9 safe area) to avoid cropping.
Avoid chip lists; embed replies/actions in cards instead.
Test flows on both iOS and Android before launch.