Ask HN: DIY storage or not?
We have developed a generic syncing app (web, desktop, mobile) on top of cloud storage (S3 initially). We are moving to testing soon and can offer either a hosted version or let customers use their S3 account. Which offering would you advice we focus and why?
Our thoughts:
1. Focusing on latter differentiates us
2. Allows us to "plug" into future cloud storage (Goog, Msft, etc)
3. However, not sure if market today is "too niche"
4. Audience is individuals and businesses
Thanks in advance.
(
13 comments
| 13 points
| on HN
)
Is entering your S3 secret ID and key too cumbersome for most customers?
In addition, storing their S3 credentials has all its own problems. Remember that the AWS credentials are pretty powerful. If your database is compromised, those keys could be used to drain peoples' bank accounts via Flexible Payment System (FPS). Handle AWS credentials as you would a credit card number, which means avoid at all costs!
FWIW, "control my own storage" is overhead for almost everyone; it is overhead that they'll pay to avoid.
Is there something that precludes you from offering the option to use either (or even both), like development time?
So I would say, 3.
Similarly, mp3 players weren't killer products until iPod came along :)
+ chances are if a person has an S3 account, they most likely have the knowledge to do what you are doing themselves