.



A powerful, highly customisable, script-able and cross-platform application to build watch faces for TicWear, Tizen and WearOS watches. The builder application is also available on iPhone as well as Android. It is even possible to make APK's of your Watch to sell on Play to other Watchmaker users. Watchmaker now even boasts it's own store for professional watch makers to make money from all their hard work!

Whether you just want a massive collection of pre-made faces or make your own from scratch, Watchmaker lets you do this! With it's WYSIWYG interface, even people with no coding knowledge can make beautiful faces. It's also spiced up with Lua, a very simple and powerful scripting language that can empower you to make extremely detailed and functional watches.

The official Wiki for Watchmaker can be found here: http://watchmaker.haz.wiki

Whilst I kept meaning to make an account on the original WiKi, I thought it'd be easier to place my versions here. If a user of the official WiKi wishes to copy any or all of these pages onto the official Wiki, please do! You can get a page source view to simply copy and paste by using the menu bar to the right. WikiD Instructables provides this documentation under the same license!

Whilst I am not a graphical designer in any sense (take a look at how basic I wanted this site!), I still have a collection of watches. Whilst I do have a few stable and complete watches, my collection provides a wealth of code examples, proof of concepts and some special hackery.

My Watchface Collection

Watchmaker has a simple integration to Tasker. With the power of Lua, this can be manipulated to a great degree. I aim to provide insightful methods on how to manage Tasker with Watchmaker. I only got into Tasker because of Watchmaker, so I have 4-5 years of experience to share.

Watchmaker can receive variable and variable contents from Tasker. This includes things like your SMS content, last call data, name of WiFi among many more bits of information. Any alphanumeric data you can get into Tasker, can be fed to Watchmaker.

Handle variables

A variety of tricks I use to handle Tasker variables to make error checking requirements lower.

Watchmaker can run Tasker tasks. This allows you to run your favorite tasks, get data fed back to watch and pretty much anything else you can do by executing Tasker tasks. Tasks could then send variables back to Watchmaker.

Run Tasks from scripts

How to run Tasks from the script instead of ontap.

Change WM Faces

Tasker can change between installed Watchmaker faces installed on your watch. This could allow you to make multi-screen watches without too many faces, change between desired faces depending on location, time of day or other events & conditions.

Common issues

Over the years I've learned of quirks. The following pages will hopefully identify and assist you with then most common ones!

An anonymous discussion so you can provide me feedback and ask me questions on this topic!

Discuss

Watchmaker has basic permission requirements.

• Body Sensors
  • To monitor heart and step counter.
• Calendar
  • To get information about your calendar events
• Location
  • For Maps & Weather
• Storage
  • To save and read watches

• None

• Will benefit being excluded from doze

• Flurry
  • Analytics of app usage for developer
• Google Firebase Analytics
  • Analytics of app usage for developer
• Google Crashlytics
  • Report crash and provide logs to developer
• Google Doubleclick
  • Used for targeted ads
• Google Ads
  • Provide ads in free version

This page is WiP!

Today this page has been viewed 3 times today!

• Twitter
• Reddit
• Telegram
• Email