If you're looking to simply capture any binary data, Chute is not the ideal option. While we will offer access to even more sources than we have today, we're not focusing on the capture of documents, presentations or other non-media docs.
If you definitely need media, then we think we're a great solution since our tools only work with those types of files. That means that not only do we spend a lot of time working through how they arrive and get processed, but also in how delivered back to your users.
This leads me to my point about workflow. We've seen and learned that every app wants to use media files in different ways. That creates a number of unique challenges as a platform: authentication, rights management, terms of use, custom metadata, custom profile data, 3rd party processing ,etc.
For many, and we'd venture most, media apps - simply putting the file online won't be enough. It will have to go through a number of steps and more often than not, there's a need to capture additional data as part of the intake. Put another way, a media file's life only begins when it gets "online".
We're focused on those use cases first and foremost and think we'll be the ideal fit for anyone who needs the same thing.
We have two primary audiences today: brands/publishers and developers.
While there's a great deal of support for developers already, we know that there's a lot more that we can do and will be rolling out a great deal of new content soon.
I think it comes down to a couple of things.
1. File Requirements 2. Workflow
If you're looking to simply capture any binary data, Chute is not the ideal option. While we will offer access to even more sources than we have today, we're not focusing on the capture of documents, presentations or other non-media docs.
If you definitely need media, then we think we're a great solution since our tools only work with those types of files. That means that not only do we spend a lot of time working through how they arrive and get processed, but also in how delivered back to your users.
This leads me to my point about workflow. We've seen and learned that every app wants to use media files in different ways. That creates a number of unique challenges as a platform: authentication, rights management, terms of use, custom metadata, custom profile data, 3rd party processing ,etc.
For many, and we'd venture most, media apps - simply putting the file online won't be enough. It will have to go through a number of steps and more often than not, there's a need to capture additional data as part of the intake. Put another way, a media file's life only begins when it gets "online".
We're focused on those use cases first and foremost and think we'll be the ideal fit for anyone who needs the same thing.