So - I helped build this with mikro. We have been bootstrapping our startup Fleck (www.getfleck.com) and wanted to take a shot at making something that had a price tag associated. We built DockPlayer in a few days, and with one email, we made it to LifeHacker!
Why it's cool: We give you access to creatives all around the world for topic based photo sharing. No more #selfies or #burritos when you just want to see Street Art or Typography photos. We have been touted as "Pinterest for the real world" by a few of our users.
I think this is the way that most people come across their usage and start using them themselves. It's almost a "under the breath" type of comment. As in "Eating dinner #ImFat" or "About to watch Halloween movies #soScared"
It might be worth noting that this particular 9 year old is really good at math, but struggles a bit with reading. Thanks for all the suggestions so far!
My cofounder mikro and I have bootstrapped Splash since last August, and we just released in the App Store last week. We are excited to share with you our work, and would be grateful for your feedback to our idea, approach and implementation.
Splash is a social network in which you follow tags, not people. Our app has been described as a mobile-only Reddit. We are focused on building a short-form social network that allows for anyone to join and participate in a virtual community around any topic. We started with photos, and eventually may add other types of content (text, video). As we grow, we plan on location playing a more central role on our platform.
The next set of features we are building include search and better discovery of tags, improved algorithms for our ‘Explore’ tab, and ways for users to invite friends to participate in individual tags.
Thanks, we look forward to hearing what you think!
For us (Splash.io), it was a matter of not having the ability to purchase splash.com, and that our URL is not really that important (we are a mobile app, App store ranking and searchability is a way bigger issue). Plus, .io seemed reasonably acceptable for our product. We also nabbed getsplashapp.com, but splash.io is shorter, and I think easier to remember.
So there is definitely no unified inbox? That to me is a deal breaker. I couldn't tell from playing around with it if I was somehow missing a unified stream somewhere.
Well, added Splash to the list. It was funny to see at least one other company very similar, and that is launched! At least we know we are headed in a good direction. :)
I think I would disagree. I think there are plenty of really bad ideas that people are pursuing in one way or another. I think there is at least some value to the idea to start with. It is, after all, the building block upon which a startup gets going.
I wonder - do you think the great experiment for 'no idea' applications is going to be abandoned after the upcoming class?
There is such a consensus of thought in the startup world that "ideas are useless, it's all about execution." But, I think this is flimsy thinking. Amazing execution with a shoddy idea doesn't benefit anyone. This account seems further validation of that thought.
I think a great idea has the opportunity to build consensus among founders and aid in forming a team. It seems nearly impossible to find other people to join existing ideas and be as passionate about their promise and future.
This is great work! I could see a form of this being pushed out by Apple, maybe if it were a bit more streamlined and simplified? Not sure how to do that, since you have done a very good job already of making it intuitive IMO.
I'm not entirely sure what your distinction is between hardware and 'product.' I would argue that 'product' as you argued for should be a meeting of hardware, software and UI/UX. Any one (or two) of these items on it's own pales in comparison to a healthy balance of all three.
Hopefully other airlines will follow suit. Airlines find any reason they can to upsell passengers, so it is refreshing to see one that will be rolling out a service for free. This fact alone makes we want to support their business.
To elaborate... What informs my thought process as to what I believe will happen when using the interface? Do I think it will behave a certain way because it seems to make the most sense, or because I remember the iOS implementation? Since it's probably fair to assume that my understanding of any UI is going to be derived from some other previously used UI, perhaps the question is a pointless one? I am not sure what the answer is.