|
|
|
|
|
|
by dirtae
4073 days ago
|
|
|
We chose not to build an Apple Watch app prior to its launch precisely because it difficult to do good design and engineering for a device that you don't have and have never used: http://blog.anylistapp.com/2015/04/why-anylist-is-not-availa... See also: http://www.macrumors.com/2015/04/29/qantas-customers-discove... 'Qantas's predicament serves as a sort of warning for developing an app for the Watch before actually having the device in hands to test. Qantas's lead app designer, Gabriel Santos, echoed a similar sentiment of difficulty in developing the app, describing the entire ordeal of building and creating the app without the Watch "a scary process." "We initially locked in a concept but when trying it on the actual device, it didn't work as well as I thought it would," he said.' |
|
|
The best way I ended up trying to get a "feel" of how this would work, was to add the designs to Flinto on an iPod touch, then covering up the rest of the screen except for the Apple Watch size. That way we could scroll around, etc. It worked for the feel of the size, but it's not a replacement for the real world use of it, of course.
There were definitively a few ah-ha moments when using it for the first time on an actual device, but I do feel we hit the experience pretty well. Apple has also featured the app as one of the best new apps for the Apple Watch, which is pretty awesome :) But yeah, completely understand your reasoning.