Show HN: Dead simple photo sharing
Hi all, about a month ago my wife was complaining about how annoying all of the photo sharing services were. Either the UI was overly complicated or it would ask people to register for the service before they could view the photos, etc.
So I decided to build something dead-simple that she could use. There are no frills. You just create an album and email it around. The link goes directly to the photos.
It's not fancy at all (very utilitarian), but she appreciates it, so I thought I'd launch it as a full service and share it with people.
It's called SimpleNeat http://www.simpleneat.com
If people try it out feedback would be appreciated.
57 comments
[ 2.8 ms ] story [ 96.0 ms ] threadhttp://www.simpleneat.com
Awesome job.
Only question is regarding the switch between view-only and collaborative. When I choose to allow friends to contribute to the album, the provided link doesn't change.
I assume you have a view-only link and an edit link that is passed a var to allow people to modify it. How does this work in your application?
It could be something as simple as selecting "Yes" generates an edit var with the associated link. If someone pastes the edit URL into their browser and the edit var = the album id, allow edit. Else force view only.
Edit* This is just an opinion and what logically makes sense to me. Would love to hear what others think.
I'd certainly consider tweaking it, though, to make it possible to share a view-only and collaborative album simultaneously.
Quick question. Would it be ok if you clicked a link and then it emailed you a bit later when the download was ready?
Out of curiosity why do you want to view the full-resolution photos vs. the ones that are scaled to fit your screen?
There's now a link next to the "Download Photo" button called "View Original" when you click to view the larger photos.
Update
Unfortunately on Chrome this link doesn't work because the photo is stored in a way that tells Chrome to automatically download the photo. I'll have to dig in to figure out if there is a way to force the photo to be displayed instead of automatically downloaded.
Overall, it looks great. My family would definitely use it, for similar reasons to yours. Nice work!
You want "Content-disposition: inline" or no content-disposition header.
However, since I can use it without an account, why would I register? You may want to add some motivational copy to the registration page to tell me.
Also, these two statements from the "Free" section don't seem to match: * Original, full-size photos are stored for one month. * Full-sized photos can be downloaded for $0.99/album after one month.
Maybe the second one should be "for up to one month"?
The second line is meant to explain that after one month you can pay $0.99 and download all the full-size photos (before one month you can do that for free). Is that how you understood it?
What happens with the photos if you cannot afford to run the service?
You say no registration required but next the create album button are sign in and register buttons. I'm sure there would be some users who think they need to register/sign in before clicking the create album button.
I also don't see on the home page what I would get if I did register (even though it's not required).
You don't really get much through registration right now other than a simple way to keep track of the photo albums you've created...
That's what I would have guessed. I don't think it's that big of a deal but it might be confusing to some users, especially if you are targeting less tech savvy people looking an easy way to share.
(And you do escape input for the album title. So this looks like an oversight.)
Well done on your site. It's simple enough.
The difficulty in this space is that you have to be on as many platforms as possible. By definition, most events have users with multiple platforms. Android, IOS, etc...
We allow users to contribute to an album via Hashtag, emailing photos to a custom email address, and native mobile apps on android and IOS. This tends to be very difficult and even harder if you try to use trigger.io or sensatouch or a similar such system. Building native is hard.
Every month we see 2 to 3 new startups in this space.
Cheers.
I made a very simple photo hosting service almost a year ago http://img42.com (it leaned more towards temporary hosting though).
But yeah might just be because I'm so used to iOS but who knows.
When I try to get a full-size version of my picture after uploading it I get an error message:
"We're sorry, but something went wrong.
If you are the application owner check the logs for more information.
I was just making some changes to the site to fix a bug and introduced another bug :) It should be fixed now.
Just one critique. It looks a little too... neat (like it hasn't been lived in). The images on the home page that are so integral to the look, come across as stock photo'ish (even though I'm guessing they're not). It might just be that the three home photos look like they're from the same family trip.
Also an aside - and I hate this part - get yourself a privacy / terms / dmca / takedown request section as soon as reasonably possible. If you plan to let the public have at this, you're going to get all sorts of terrible shit uploaded sooner than later. You can probably mostly clone Imgur on this.
Good point about the privacy terms. I have examples from my other websites that I'll throw up there.
BTW: welcome to 2014 :)
© 2014 Irrational Design Contact