Hacker News Reader

Comment by leetNightshade | Hacker News Reader

Why does it have to be an app? I don't have an iPhone and don't intend to get one, so I can't even try out your project.

View on HN

A mobile app makes sense for one reason: geo-location. Your phone knows where you are, so it can find lunches instantly without having to do anything. And that's the one thing you keep with you on your way to lunch, you don't carry your laptop around usually :-)

EDIT: also, notifications are important, you want to know whether your lunch is on or not. Emails would work too, but that's kind of old school.

Geolocation is possible in a web app as well, and is supported by both desktop and mobile browsers: http://caniuse.com/#feat=geolocation

True. Don't take this the wrong way: As a programmer, I would also add that it was a pleasure to work with a real UX API again, and not have to deal with HTML's crazy issues, centering text, jQuery, browser incompatibilities, etc. I always had a <div> that didn't quite work the way I wanted.

In the end, a native app looks much better for fewer lines of code (assuming you can stand Objective-C).

But if it was built in html, js, etc it'd be accessible on all platforms for far fewer lines code than building separate apps.

MVP priority list for a calendaring application:

#1 UI looks pretty #2 Functionality is avaialble to potential users.

It would also be handy if it worked without location services... just let me enter a suburb/ city.

Reply on news.ycombinator.com