152 karma · joined September 30, 2009
It gives a reminder to drink water any time it's been three hours since you've peed...
https://itunes.apple.com/us/app/pee-see-drink-more-water/id1...
Not super scientific, but less of a hassle than tracking water input and it tends to adapt well to factor in things like exercise where more water is needed. It also tends to even out over time when drinking alcohol or coffee. Urine color can also vary depending on foods, like how B12 makes it fluorescent yellow, so the time factor can be another useful indicator.
But yep it just pulls the lat and lon from the EXIF data, so it should work fine. The standard for EXIF is degrees, minutes, seconds and then a separate "Ref" value for N or S.
I have to do a little math on those values to turn everything into a decimal format, but based on this standard I would assume everything saving location in EXIF data would use this same format so it should all be compatible:
http://www.exiv2.org/Exif2-2.PDF (See page 53 of the PDF under the heading GPSLatitude)
If you test it, let me know!
Try rotating your phone around in a circle a bunch and then see if the compass starts moving and correcting itself.
The reason I tried JavaScript first was to start off cross-platform, but when that failed I developed for the hardware I use.
However, I've been meaning to try out some Android development, so maybe at some point...
The map doesn't show your location, and even if it did you would still need some kind of compass arrow, like the Google Maps app for iOS shows, to be able to navigate to it.
Also, this works by pasting a photo from the clipboard instead of just using photos in your library.
Also, I apologize for the buggyness with that swiping... I should have used a UIPageViewController and will probably go fix it at some point.
You can read more about all this in my blog post, including the decision about distance units.
Cool idea about the collections.
Another extension of it I also thought about is a version with some kind of node.js backend that's a little bit like Yo except whenever you and a friend have it open it points you at each other so you can find each other on foot as long as you have a decent internet connection and good GPS accuracy.
It lets you pick a photo you took (or that someone sent you) and then points you in the direction the photo was taken, kind of like a compass, based on the coordinates stored in the photo's EXIF data. It's basically a fast and easy way to mark locations and get back to them.
Originally I tried it in JavaScript, but iOS strips lat and lon info from photos when they're picked with a file input field. You can still find the beginnings of my hacked together JS version here: http://foodsfofree.herokuapp.com/
This is just a side project I built for fun since I hadn't built an iOS app before, so I'm not trying to turn it into a business or something, just wanted to share it!
You can also read more about it here on my blog: http://gohnjanotis.com/photo-find-v1-1-released/
It's like some people want a BMW just to impress the neighbors with a badge, while others can appreciate the level of engineering and the minds that went into the precision you can feel when you are driving it.
I like to make purchasing decisions based on the competency of the company in making what they make, but unfortunately most people don't think that way so a phone like this doesn't even get a chance.
We recently struggled with this on the design of the front page of an application. A similar issue we ran into is scaring people away with login/password boxes on the front page.
What does everyone think, is it better to have the login/password boxes visible immediately to save the user a click, or do what digg and twitter do to avoid scaring people about a sign-up form in the not so distant future and hide it behind some AJAX?
This kind of low-power application is GREAT for solar panels. I'm sick of people trying to put them on everything (like electric cars... do you know how impractical it would be to put them on a Tesla based on their current efficiency and cost?)
For example, intense BitTorrent downloading (and uploading) on a RAM disk frees my hard disk from the constant reads and writes so I can have high speed downloads (and verification of d/led data) and still do disk intensive activities in other applications.
I can't wait for the day where my mass storage can have that kind of speed! (and it looks like it's closer than ever now)
They need to let the market decide.