Ably is already a powerful and reliable platform for real-time communication. Some areas where it could be improved are by providing more advanced analytics and monitoring tools, more detailed documentation with real-world examples, and easier setup guidance for new users. Additional integration and continuous improvement in performance and developer experience would make it even more useful. Overall, Ably provides a strong real-time communication solution, and these improvements could make the experience even better. I would like to see more advanced monitoring and analytical features, improved dashboards for tracking real-time events, and more detailed documentation with practical examples. Additional integration and easier configuration options would also make the platform more user-friendly. These improvements would help users understand performance better, troubleshoot faster, and get more value from Ably.
Every software platform has opportunities for improvement. The first improvement I see is that local development and testing experience can be improved. Testing real-time flow locally can still be challenging for us, and better tooling for mocking or simulating Ably events, along with better support for testing reconnections and failure scenarios, would help our teams validate behavior before moving to production. While basic metrics are available, deeper observability could be beneficial, including enhancements such as more granular and real-time dashboards, easy integration with third-party monitoring tools, and clear visibility into message flow and latency. Regarding pricing, usage-based pricing can sometimes be hard to forecast at scale, and our teams may want a clearer cost estimation tool. Improved cost visibility and forecasting would help with budgeting. Ably should provide more pre-built patterns or templates for chats and notification collaboration features, which could further speed up our process and adoption of Ably.
I wish the real-time notifications can be improved a bit more. Everything seems to be fine about the needed improvements overall. Ably is very highly reliable. I choose nine out of ten because the notifications part can be seen to improve further. In some devices, it comes early, and in some, it doesn't, so the latency part needs improvement.
Ably provides a real-time communication platform designed to manage complex streaming data and messaging, delivering reliability and scalability. It facilitates seamless integration with global messaging services, offering low latency and high availability across networks.Ably is crafted to support a diverse range of use cases including real-time dashboards, live chat applications, multiplayer games, and collaborative tools. It offers versatile API support and ensures data integrity. Through...
For the use I have made, I didn't see any limit or margin to implement to go higher.
Ably is already a powerful and reliable platform for real-time communication. Some areas where it could be improved are by providing more advanced analytics and monitoring tools, more detailed documentation with real-world examples, and easier setup guidance for new users. Additional integration and continuous improvement in performance and developer experience would make it even more useful. Overall, Ably provides a strong real-time communication solution, and these improvements could make the experience even better. I would like to see more advanced monitoring and analytical features, improved dashboards for tracking real-time events, and more detailed documentation with practical examples. Additional integration and easier configuration options would also make the platform more user-friendly. These improvements would help users understand performance better, troubleshoot faster, and get more value from Ably.
There is nothing much to be improved. The experience has been smooth so far, and I haven't run into any major gaps during technical work.
Every software platform has opportunities for improvement. The first improvement I see is that local development and testing experience can be improved. Testing real-time flow locally can still be challenging for us, and better tooling for mocking or simulating Ably events, along with better support for testing reconnections and failure scenarios, would help our teams validate behavior before moving to production. While basic metrics are available, deeper observability could be beneficial, including enhancements such as more granular and real-time dashboards, easy integration with third-party monitoring tools, and clear visibility into message flow and latency. Regarding pricing, usage-based pricing can sometimes be hard to forecast at scale, and our teams may want a clearer cost estimation tool. Improved cost visibility and forecasting would help with budgeting. Ably should provide more pre-built patterns or templates for chats and notification collaboration features, which could further speed up our process and adoption of Ably.
I wish the real-time notifications can be improved a bit more. Everything seems to be fine about the needed improvements overall. Ably is very highly reliable. I choose nine out of ten because the notifications part can be seen to improve further. In some devices, it comes early, and in some, it doesn't, so the latency part needs improvement.