Optimizing for happiness, put in the context of actual real-world happiness, is a strong point. I'll keep praying about it...
702 karma · joined May 29, 2010
Optimizing for happiness, put in the context of actual real-world happiness, is a strong point. I'll keep praying about it...
User experience - You can still create a better experience with a native mobile app, but that's changing and many apps don't require the snazziness of a native experience to still be amazing. (See Basecamp mobile)
Discoverability - The web hasn't changed much, but the app stores are hurting themselves. Vibhu's point that discoverability and the viral loop is VERY hard on mobile is illustrative of the lead that native mobile had in discoverability diminishing.
Offline - Although HTML5 can handle much of that problem on the web, I think a really great offline experience still requires a native mobile app. However, the increase in connectedness and the realization that most apps don't need to have offline at their core means the gap is narrowing as well.
Although TC sometimes feels like a tech-tabloid, I do believe it serves a better purpose.
But nature is terrible at defining and shaping human relationships. We confuse "love" with affinity. "Love" is more like a verb that entails sacrifice, acceptance, and patience...along with affinity in a marital relationship, of course.
It cripples the rumor mill, taking away the secretive intrigue. If it's out in the open, people have less to speculate about and less to talk about.
It makes it possible for us to help other couples going through it. Dealing with this can be an incredibly lonely experience. We want to help make it less lonely for couples.
Keeping it a secret doesn't help anyone and it's only built on the social need to keep up appearances. That's useless in a world where the only people's opinions that I care about are my family's.
Programming: learning by doing instead of by reading. I started learning Rails when I wanted to build PicDigest and the mistakes I've made have helped me learn faster on a broader foundation.
Excellent way to figure out how much to charge.
My company (PicDigest) is betting on a paid web-first model and planning a mobile app as a companion, even in the crowded space of photo sharing where incumbents supposedly have the market sewn up. Yes, it's a long-shot play, but the wager is based on the assumption that many people will pay a little money for what I'm offering.
I launched PicDigest a few weeks ago. I'm curious about which photo lab you use as I'm planning to add photo printing in the future. Would you mind sharing? If you want to keep it semi-private, you can email me at scott@picdigest.com.
If you're going to hire a design employee, that's an entirely different discussion with lots and lots of variables.
I applied as a solo founder, so I'm really not surprised.
In other news, I'm considering bringing on a technical cofounder that can take over with what I've built with my very minimal Ruby knowledge while I handle everything else. :)
Hold the account-setup step until I've created my first project and want to do something with it. That's when I'll be able to easily understand why I need an account.