Skip to content

[EDU-2094] - Update Chat docs landing page to improve the reasons to use #2863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[EDU-2094] - Update Chat docs landing page to improve the reasons to use #2863

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 66 additions & 9 deletions src/pages/docs/chat/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,72 @@ Ably Chat is a product dedicated to making it quick and easy to build chat funct

The Chat SDK contains a set of purpose-built APIs that abstract away the complexities involved in how you would architect chat features. It utilizes Ably's platform to benefit from all of the same performance guarantees and scaling potential.

* [Getting started: Chat in JavaScript / TypeScript](/docs/chat/getting-started/javascript)
* [Getting started: Chat in React](/docs/chat/getting-started/react)
* [Getting started: Chat UI Kits in React](/docs/chat/getting-started/react-ui-components)
* [Getting started: Chat in React Native](/docs/chat/getting-started/react-native)
* [Getting started: Chat in Android](/docs/chat/getting-started/android)
* [Getting started: Chat in Kotlin (JVM)](/docs/chat/getting-started/jvm)
* [Getting started: Chat in Swift](/docs/chat/getting-started/swift)
## Why Chat
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this 'Why Ably Chat'?

I think we should then have some content under this heading that covers the fact that Chat is built upon Pub/Sub and also the platform (need a good way to word both of these ideally).

We then have some redundancy with the final sentence in the previous paragraph.


### Built for Serious Scale & Reliability
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sentence case and no ampersands please 🙂


Ably Chat is powered by Ably's globally distributed platform that handles **550 billion messages per month** and **1 billion+ connections per month**, serving the world's most demanding workloads with **100% uptime over 5+ years**. With a global edge network featuring **635 points of presence**, Ably Chat delivers messages with **<50ms median roundtrip latency** and provides automatic multi-region failover to ensure your chat experiences are always available.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth splitting the scale part and reliability part into separate paragraphs here, otherwise you get a a lot of 'withs' together, and a lot of bold text. Might also need some revision with an updated section above that covers it being built on the platform.

We should also link out to the platform section, or architectural section when discussing these numbers.

Should '550 billion' have a + ?


### Cost-Effective Scalability

Scale without penalty using Ably's usage-based pricing model that charges by-the-minute for what you actually use. The platform includes built-in cost optimization features like **message batching** to reduce consumption, and **volume discounts** that lower your overall cost as you grow. This means you can power more chat functionality within budget without stifling innovation for fear of cost.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only covering usage-based pricing and ignores MAU.


### Developer Productivity

Get building with intuitive APIs and comprehensive SDKs across multiple platforms. The Chat SDK abstracts away architectural complexity, enabling your team to rapidly ship exceptional chat experiences. Pre-built **React UI Kits** and **React Hooks** accelerate development even further, letting you focus on creating unique experiences rather than building chat infrastructure from scratch.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs a little thinking on how it flows into the getting started guides (should it be combined?) and the 'features' section further down.

I'm not sure hooks warrant being called out as that's expected in a React package I think.

Might also be worht pulling out UI kits separately - or look whether that should be part of the 'features'?


### Enterprise-Ready
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd swap this around with the 'develop productivity' as that leads into the getting started guides.


Ably Chat supports enterprise requirements with **HIPAA and SOC2 compliance** options, dedicated clusters, custom domains (CNAME), SSO integration, and premium support with **sub-15 minute response times**. Whether you're building for thousands or millions of users, Ably Chat scales with your business needs.

## Get started now <a id="get-started"/>

<Tiles>
Comment on lines +30 to +32
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need some sort of run on, or intro text about SDK availability (similar to what you covered in the dev productivity section.

We should likely still pull UI kits out separately too IMO.

{[
{
title: 'JavaScript / Typescript',
description: 'Start building with Chat using Ably\'s Chat JavaScript SDK',
image: 'icon-tech-javascript',
link: '/docs/chat/getting-started/javascript',
},
{
title: 'React',
description: 'Start building with Chat using Ably\'s Chat React SDK.',
image: 'icon-tech-react',
link: '/docs/chat/getting-started/react',
},
{
title: 'React UI kits',
description: 'Start building with Chat using Ably\'s Chat UI components with Chat React SDK.',
image: 'icon-tech-react',
link: '/docs/chat/getting-started/react-ui-components',
},
{
title: 'React Native',
description: 'Start building with Chat using Ably\'s Chat React Native SDK.',
image: 'icon-tech-reactnative',
link: '/docs/chat/getting-started/react-native',
},
{
title: 'Kotlin (Android)',
description: 'Start building with Chat using Ably\'s Chat Kotlin SDK for Android.',
image: 'icon-tech-kotlin',
link: '/docs/chat/getting-started/android',
},
{
title: 'Kotlin (JVM)',
description: 'Start building with Chat using Ably\'s Chat Kotlin SDK for JVM applications.',
image: 'icon-tech-kotlin',
link: '/docs/chat/getting-started/jvm',
},
{
title: 'Swift',
description: 'Start building with Chat using Ably\'s Chat Swift SDK.',
image: 'icon-tech-swift',
link: '/docs/chat/getting-started/swift',
},
]}
</Tiles>

## Chat features <a id="features"/>

Expand Down Expand Up @@ -76,8 +135,6 @@ Take a look at a [livestream basketball game](https://ably-livestream-chat-demo.

## Next steps <a id="next"/>

* Read the [JavaScript / TypeScript getting started guide](/docs/chat/getting-started/javascript)
* Read the [React UI Kits getting started guide](/docs/chat/getting-started/javascript)
* Read more about using [rooms](/docs/chat/rooms) and sending [messages](/docs/chat/rooms/messages).
* Read into pulling messages from [history](/docs/chat/rooms/history) and providing context to new joiners.
* Learn about how to add [chat moderation](/docs/chat/moderation).
Expand Down