HotelQuickly Apple WatchWhat we have learned…… so far….

Why did we make a HQ Apple Watch App ?

• We believe it will enhance our users experience

• We wanted to be right at the forefront of current technology

• Exciting for us, as developers, to be involved in

• Obvious potential for PR

• Early adaptation gives the best insight to the tech in the longer term

So Michal (CTO) said…‘Let’s Do it’!

Do your homework!

• What is the device capable of ?• Who are your customers ?• How should they use your Watch App ?• Will your idea be possible technically ?• READ APPLES GUIDELINES!• Get your design and UX outlined……

What next ?

1st draft nth draft

and finally…

The development process• Full lifecycle took 6-8 weeks

• Apples’ ongoing collaboration was extremely insightful

• Technical learning curves everywhere

• Adding Watch App extension to the project

• Setting up HandOff

• Creating app-groups

• Very limiting WatchKit framework

• Lack of a physical device ( although we got access to an Apple Watch Lab in Hong Kong)

• Changing the mindset of the product team

• Unknown Watch App review process

The finished product!

Apple Watch Do’s1. Keep it simple

2. Expand upon existing features in your main app

3. Ask your customers/friends what they would want

4. Keep content/text clear 15-16px for easy readability

5. Use and love ‘HandOff’

6. Use ‘app groups’ to share data between your main app/watch app

7. Think of it as a new platform.

8. Keep it simple

9. If you can, leverage the native features on the watch e.g ‘Maps

10.Test on a physical device. You will learn a lot about your app

Apple Watch Don’ts1. Try to avoid direct replication of your main app

2. Have more views than necessary

3. Use a menu that is not relevant to the view

4. Use a button for a ‘Handoff’ event. Keep it fluid

5. Have too small font

6. Make the watch perform too much heavy work

Any questions ?