As a developer, I find Cloudinary valuable because it provides many opportunities for building applications. For example, I recently created an AI application that can read images and automatically generate captions, which helps in describing images or videos without manual input. Cloudinary's APIs support this functionality and enhance my development process.
One of the most beneficial features of Cloudinary is its asset management capabilities. I can tag and categorize images and videos based on their content, such as tagging videos where a person is wearing glasses. This helps in organizing and managing media effectively.
I have experimented with Cloudinary's automation capabilities, but I am still learning and haven't fully explored its potential. Currently, I want to use Cloudinary to improve user engagement with my videos, such as tracking who is viewing and interacting with my media. This is a feature I plan to explore more in the future.
I like the tool best because it's straightforward and doesn't have too many complicated options like AWS. The dashboard is clear - you create a directory, get credentials, and then use those in your Node.js or Java application to access resources. With AWS, you have to consider many things, like bucket policies and user permissions. It doesn't have these complications. Everything on Cloudinary is clearer than other platforms I've seen. It is very easy to use. It's easier than the AWS platforms I've seen. Even general developers can use it, while AWS needs more experience.
Staff Mobile Engineer at a tech services company with 10,001+ employees
Jul 8, 2024
Unlike Firebase Storage, Cloudinary handles media-specific tasks like re-encoding uploads. For example, when users upload a video from an Apple device, it's often encoded in a proprietary Apple codec.
One of the best features of the platform is that we have a generous free tire that I can use for some of my projects without worrying about the platform's cost.
I haven't really thought about what improvements I’d like to see in Cloudinary recently. One thing that comes to mind is the capability for hosting very large video files, similar to platforms like YouTube. Cloudinary is not as widely known for video uploads as other platforms, and it would be great if it had a larger user base for this purpose.
Apart from marketing and video uploading, I haven't identified specific features or functionalities that need improvement. It’s been a while since I actively used Cloudinary, and I’m just starting to get back into it. Once I’m more familiar with it again, I’ll have a better idea of any gaps or areas for enhancement. I’ll need to think more about this and might provide feedback later.
I think Cloudinary has room for improvement, depending on the project you're working on. Changes might not be needed if your project fits what Cloudinary already offers. But if your project needs some changes, you can make them.
Staff Mobile Engineer at a tech services company with 10,001+ employees
Jul 8, 2024
The main issue with the package is how it handles errors. It swallows errors and throws its own, but without preserving the stack trace, making debugging nearly impossible.
I believe there is some scope for improvement in areas like the dashboard, specifically the user dashboard and the browser where you can navigate the platform.
