Thanks. Fixing that link sounds like a tangible next step for improving my "mini-app". I think I'll take it farther just because, like making it work for a couple more stops and setting up a better time input.
I really like that it's instant and super lightweight. Those are valuable traits.
You might want to consider carefully how you change the time input. What you have now is the minimum possible input to specify a 24 hour range. You might want to take input like 115, 10 20, and put effort into parsing any input, rather than fixing the input at something that involves, say entering a colon (shifted character and harder to input on a phone), which might look more professional, but is actually a giant step backwards!
For people that are just 'starting out' and also people that just want to keep their hand in, it's really a good idea to practice writing small pieces of intricate code like tokenizers, string processing etc., rather than just selecting the closest library to hand.
Obviously, if you're writing code commercially, you may want either complete control over some code (write it), or you may want it now (use a lib), so writing all your own code may be an impossible luxury.
Here's a small example snippet I just did. I've been doing software since 1988, but often just gluing (MFC) api's together, and not doing stuff that really benefits me as much as it might. Anyways, here's a gist that implements a 'good enough to use' version of an iOS 4.0-only api as a category on NSData, allowing string searching of arbitrary data:
