Preparing a macOS app for distribution through the App Store is fairly easy using Xcode, but to do so for apps that you plan to distribute as a binary by other means — as a download from your own website, for example — isn’t straightforward, and it has got more complicated over recent macOS releases.
Update Pebble has released version 2 of its OS and this invalidates much of what follows, which was written for an earlier version of the OS.
As it stands, the app I created in Part 2 appears in the Pebble’s menu simply as a name, Ball, which is entered into the boilerplate PBL_APP_INFO created by the SDK’s create_pebble_project.py script. This also sets the app’s unique UUID, which you’ll see at the top of the file. You can also modify this to set the app’s version number and to add your name as author. But what’s really needed is a menu icon, and you can add one by editing the resource_map.json created for you in the /resources/src folder within the project folder.
Update Pebble has released version 2 of its OS and this invalidates much of what follows, which was written for an earlier version of the OS.
In Part 1 we got our basic Pebble app up and running, but it doesn’t do very much. Let’s add some user interaction.
Update Pebble has released version 2 of its OS and this invalidates much of what follows, which was written for an earlier version of the OS.
Pebble didn’t invent the smartwatch, but it has done more than most to bring this new product category to the attention of the world, largely thanks to its hugely successful and well-reported Kickstarter funding campaign.
smittytone messes with micros 