diary.io - should we build this?

You should build this if you want to build it. It's something you can point to and say "Look, I built something awesome!".<p>But, chances are this will not be able to make money as it (1) requires user setup (2) will be fairly difficult to build - api integration is not that easy (3) most users simply don't care about what happens to their data until it is gone.<p>(3, my experience) goes directly against your Thesis #2. (1) goes against your Thesis #3 - users generally are not forward thinking enough to do something now that will only benefit them later. I'd say start on actually trying to test your Thesis #1-#3 before assuming them correct.

1. There are already services to "backup" your socially posted content <a href="http://jolicloud.com" rel="nofollow">http://jolicloud.com</a> <a href="http://socialfolders.me/" rel="nofollow">http://socialfolders.me/</a><p>2. Cross posting to multiple services is really, really hard. Each service has a different number of fields. You would have to get the user to complete the full information for each service in one go. Technically you could map all these fields, but from a UX point of view it's really hard.<p>3. Most services cross post between other services already. At least in a way that matters to most. And there are various ways that are "good enough"<p>Having said that, yes there is a demand for this. I've heard it direct from my customers. I actually work the other way in that I aggregate what you already post socially.<p>But I would look very hard at the financial side on this, I'm not sure you'll make enough money to warrant the effort.

You're asking the wrong people.<p>1. Read "The Lean Startup."<p>2. Find the cheapest and fastest way to test whether potential customers think you should build it for them. For example, you could make a fake product web page with a "try free" button and count the number of people who click the button.<p>Asking us is not lean. Asking customers is not lean. Testing customers != asking them. Building it is too expensive a test to be lean.<p>Gotta run, can't put more words into this, sorry!

Guys, I really love the "shouldwebuild" this concept! This is a great way to validate an idea. Can I borrow it for my concept please? :)

If you're going to ask visitors to answer questions, don't force them to read over things they don't need to know before getting to the meat of it. Just say "Here are some concepts for a _______ app/service, based on these screenshots, would you actively use this tool? If no, what features would you need to use it?"<p>That said, the response will be from so many different people with different ideas of their ideal solution to this that it shouldn't used to determine the worth. People will try something if it exists, and they'd rather waste their time trying to use it than answering questions about what <i>it</i> is.

Nope, because:<p>(engineer * number of engineers) - (average monthly payment * number of customers) &#60; 0<p>An engineer's salary at a small startup is at the very least $50,000, let's just round that down to $5,000 a month, so how long do you think it would take you to reach $15,000 a month in recurring revenue at what are probably $5 a month plans (this does not include any other costs such as office, servers etc). That's about 3,000 users. And that's just to pay a very poor salary with no other kind of expenses.

Nope, because you didn't believe in it enough to build it, instead choosing to waste time posting on websites. Zuckerberg didn't ask if he should build Facebook, the GitHub founders didn't ask if they should make GitHub, and Jason Fried didn't ask if he should build 37signals.

I hope if you build it, you charge. I really don't think the world needs another remix of social for the average users. "Should" should be based on your needs (if you want to work for free, let me outsource some of my work to you), not whether or not the socialsphere needs it.

I think if there is value here, it is not so much in the backups and crossposting, both of which are available already. It would be in helping people manage their various personas or public image. And that would take something more than just tech tools.

I would use it and I know a ton of other people who would too. Is it the next industry dominating creation? No, but I believe any service built on the backs of other services hardly ever are. The product path isn't unique enough and in the end you always rely on another business for yours to do well. Blah... It would be a ton of fun to build though and you’d make a lot of people very happy to have it, which is really why we all do what we do. Official label suggestion from me: Hobby Side Project. Build the cortex and open it up to the community for tweaks.

I think the question is "why"? Is this a tool you hope to go mainstream? Why this over IFTTT? Is this a big opportunity?

"Further, the image file as well as its metadata would be backed up to your own little piece on the cloud"<p>Doesn't seem like much of a backup to me... I'd hope at the very least that even if there isn't a local storage option they would build it to support other peoples "cloud storage" products.

Just a minor thing, but you should use smaller mockup images, because the automatic down-scaling is incredibly poor and results in a really jaggy image.<p>`width: x%` is always going to lead to poor image-scaling, but it can be mitigated somewhat.

There should be an option to tell you I would not use or pay for this service.

Diary.io Diary.io Diary.io<p>Good to see you man! Heard your pitch at Startup Weekend Delhi

Mmmm, maybe for companies/marketers. I can see a tool being useful to customize/personalize your marketing effort across the various networks.<p>I don't see consumers ever paying for this, however.

I'm impressed you made it to the front page, congrats on that.

This is very difficult question to answer. Unless you actually build it in some way and ask your target audience to use it you won't get any concrete feedback.

You're trying to sell people an Idea, this is a survey.<p>Getting people to pay for stuff is not the same as asking them if they would.<p>People don't buy Ideas, they buy Value.

Yes, but (sorry to be immature) maybe register a different TLD so the product name doesn't sound so much like diarrhea?

I can't figure out what it's for. So I guess no, or perhaps improve the message.

Warning: Prospective questions are bad for your (business) health.

Yes!

please, no.

yes