Thanks! We'd love to add Canada, but for the time being are focused on the United States only – need to work on the fundamentals of the business before we get too spread thin.
And yep - route search in general is on the roadmap! We've got some pretty cool other ideas in terms of filtering.
(Aside: Realm has been great. We use it in the iOS app)
Tomorrow I'm going to write a post on all that went into making it. To be honest, it's not difficult to get into—with extensions running on top of AIR, the learning curve isn't steep. The main difficulties come from random platform bugs and poor documentation. Things like:
- Occasionally when a panel starts, the wrapper from Adobe that loads in your extension will be incorrectly sized... which leaves the panel with a giant white space at the bottom. To fix it, increment then decrement the height by one to get it to recalculate its size.
- On CS5.0 (only), the panel is rendered darker than it should be (so if you set the background color to the color the SDK tells you it is, you'll end up something that doesn't match up with the Photoshop UI (this might be mx:HTML specific).
- On CS6, mx:HTML causes a hard Photoshop crash sometimes (no idea why, it's blackbox). Posted on Adobe Forums... no one seems to know.
TL;DR: Barrier of entry is low. Strange issues make it hard. Sadly many of them are out of your control as a 3rd-party developer.
And yep - route search in general is on the roadmap! We've got some pretty cool other ideas in terms of filtering.
(Aside: Realm has been great. We use it in the iOS app)