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.
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.