mirror of
https://github.com/google/pebble.git
synced 2025-06-24 10:06:16 +00:00
Import the pebble dev site into devsite/
This commit is contained in:
Katharine Berry
parent
3b92768480
commit
527858cf4c
1359 changed files with 265431 additions and 0 deletions
158
devsite/source/_guides/appstore-publishing/appstore-analytics.md
Normal file
158
devsite/source/_guides/appstore-publishing/appstore-analytics.md
Normal file
|
|
@ -0,0 +1,158 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: Appstore Analytics
|
||||
description: |
|
||||
How to view and use analytics about your app's usage.
|
||||
guide_group: appstore-publishing
|
||||
order: 2
|
||||
---
|
||||
|
||||
After publishing an app, developers can view automatic analytical data and
|
||||
graphs for a variety of metrics. These can be used to help track the performance
|
||||
of an app, identify when crashes start occuring, measure how fast an update is
|
||||
adopted, or which platforms are most popular with users.
|
||||
|
||||
> Due to latencies in the analytics gathering process, data from the last 7 days
|
||||
> may not be very accurate.
|
||||
|
||||
|
||||
## Available Metrics
|
||||
|
||||
Several different metrics are available to developers, and are reported on a
|
||||
daily basis. These metrics can be sorted or viewed according to a number of
|
||||
categories:
|
||||
|
||||
* App version - Which release of the app the user is running.
|
||||
|
||||
* Hardware platform - Which Pebble hardware version the user is wearing.
|
||||
|
||||
* Mobile platform - Which mobile phone platform (such as Android or iOS) the
|
||||
user is using.
|
||||
|
||||
An example graph is shown with each metric type below, grouped by hardware
|
||||
platform.
|
||||
|
||||
|
||||
### Installations
|
||||
|
||||
The total number of times an app has been installed.
|
||||
|
||||
|
||||
|
||||
|
||||
### Unique Users
|
||||
|
||||
The total number of unique users who have installed the app. This is
|
||||
different to the installation metric due to users installing the same app
|
||||
multiple times.
|
||||
|
||||
|
||||
|
||||
|
||||
### Launches
|
||||
|
||||
The total number of times the app has been launched.
|
||||
|
||||
|
||||
|
||||
|
||||
### Crash Count
|
||||
|
||||
The total number of times the app has crashed. Use the filters to view
|
||||
crash count by platform or app version to help identify the source of a crash.
|
||||
|
||||
|
||||
|
||||
|
||||
### Run Time
|
||||
|
||||
The total run time of the app in hours.
|
||||
|
||||
|
||||
|
||||
|
||||
### Run Time per launch
|
||||
|
||||
The average run time of the app each time it was launched in minutes.
|
||||
|
||||
|
||||
|
||||
|
||||
### Buttons Pressed Per Launch
|
||||
|
||||
> Watchfaces only
|
||||
|
||||
The average number of button presses per launch of the app.
|
||||
|
||||
|
||||
|
||||
|
||||
### Timeline: Users Opening Pin
|
||||
|
||||
> Timeline-enabled apps only
|
||||
|
||||
The number of users opening timeline pins associated with the app.
|
||||
|
||||
|
||||
|
||||
|
||||
### Timeline: Pins Opened
|
||||
|
||||
> Timeline-enabled apps only
|
||||
|
||||
The number of timeline pins opened.
|
||||
|
||||
|
||||
|
||||
|
||||
### Timeline: Users Launching App from Pin
|
||||
|
||||
> Timeline-enabled apps only
|
||||
|
||||
The number of users launching the app from a timeline pin.
|
||||
|
||||
|
||||
|
||||
|
||||
### Timeline: Times App Launched from Pin
|
||||
|
||||
> Timeline-enabled apps only
|
||||
|
||||
Number of times the app was launched from a timeline pin.
|
||||
|
||||
|
||||
|
||||
|
||||
## Battery Stats
|
||||
|
||||
In addition to installation, run time, and launch statistics, developers can
|
||||
also view a battery grade for their app. Grade 'A' is the best available,
|
||||
indicating that the app is very battery friendly, while grade 'F' is the
|
||||
opposite (the app is severely draining the user's battery).
|
||||
|
||||
> An app must reach a certain threshold of data before battery statistics can be
|
||||
> reliably calculated. This is around 200 users.
|
||||
|
||||
This is calculated based upon how much a user's battery decreased while the app
|
||||
was open, and so does not take into other factors such as account notifications
|
||||
or backlight activity during that time.
|
||||
|
||||
|
||||
|
||||
Clicking 'View More Details' will show a detailed breakdown for all the data
|
||||
available across all app versions.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,55 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: Appstore Assets
|
||||
description: |
|
||||
A collection of downloads to help developers create and improve their appstore
|
||||
listings.
|
||||
guide_group: appstore-publishing
|
||||
order: 3
|
||||
---
|
||||
|
||||
A number of graphical assets are required when publishing an app on the
|
||||
[Developer Portal](https://dev-portal.getpebble.com/), such as a marketing
|
||||
banners. The resources on this page serve to help developers give these assets a
|
||||
more authentic feel.
|
||||
|
||||
|
||||
## Example Marketing Banners
|
||||
|
||||
Example
|
||||
[marketing banners](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-examples.zip)
|
||||
from existing apps may help provide inspiration for an app's appstore banner
|
||||
design. Readable fonts, an appropriate background image, and at least one framed
|
||||
screenshot are all recommended.
|
||||
|
||||
|
||||
## Marketing Banner Templates
|
||||
|
||||
|
||||
|
||||
Use these
|
||||
[blank PSD templates](https://s3.amazonaws.com/developer.getpebble.com/assets/other/banner-templates-design.zip)
|
||||
to start a new app marketing banner in Photoshop from a template.
|
||||
|
||||
|
||||
## App Screenshot Frames
|
||||
|
||||
Use these
|
||||
[example screenshot frames](https://s3.amazonaws.com/developer.getpebble.com/assets/other/pebble-frames.zip)
|
||||
for Pebble, Pebble Steel, Pebble Time, Pebble Time Steel, and Pebble Time Round
|
||||
to decorate app screenshots in marketing banners and other assets.
|
||||
|
||||
> Note: The screenshots added to the listing itself must not be framed.
|
||||
50
devsite/source/_guides/appstore-publishing/index.md
Normal file
50
devsite/source/_guides/appstore-publishing/index.md
Normal file
|
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: Appstore Publishing
|
||||
description: |
|
||||
How to get your app ready for going live in the Pebble appstore.
|
||||
guide_group: appstore-publishing
|
||||
menu: false
|
||||
permalink: /guides/appstore-publishing/
|
||||
generate_toc: false
|
||||
hide_comments: true
|
||||
---
|
||||
|
||||
When a developer is happy that their app is feature-complete and stable, they
|
||||
can upload the compiled `.pbw` file to the
|
||||
[Developer Portal](https://dev-portal.getpebble.com) to make it available on the
|
||||
Pebble appstore for all users with compatible watches to share and enjoy.
|
||||
|
||||
In order to be successfully listed in the Pebble appstore the developer must:
|
||||
|
||||
* Provide all required assets and marketing material.
|
||||
|
||||
* Provide at least one `.pbw` release.
|
||||
|
||||
* Use a unique and valid UUID.
|
||||
|
||||
* Build their app with a non-beta SDK.
|
||||
|
||||
* Ensure their app complies with the various legal agreements.
|
||||
|
||||
Information on how to meet these requirements is given in this group of guides,
|
||||
as well as details about available analytical data for published apps and
|
||||
example asset material templates.
|
||||
|
||||
|
||||
## Contents
|
||||
|
||||
{% include guides/contents-group.md group=page.group_data %}
|
||||
|
|
@ -0,0 +1,110 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: Preparing a Submission
|
||||
description: |
|
||||
How to prepare an app submission for the Pebble appstore.
|
||||
guide_group: appstore-publishing
|
||||
order: 0
|
||||
---
|
||||
|
||||
Once a new Pebble watchface or watchapp has been created, the
|
||||
[Pebble Developer Portal](https://dev-portal.getpebble.com/) allows the
|
||||
developer to publish their creation to the appstore either publicly, or
|
||||
privately. The appstore is built into the official mobile apps and means that
|
||||
every new app can be found and also featured for increased exposure and
|
||||
publicity.
|
||||
|
||||
> Note: An app can only be published privately while it is not already published
|
||||
> publicly. If an app is already public, it must be unpublished before it can be
|
||||
> made private.
|
||||
|
||||
To build the appstore listing for a new app, the following resources are
|
||||
required from the developer. Some may not be required, depending on the type of
|
||||
app being listed. Read
|
||||
{% guide_link appstore-publishing/publishing-an-app#listing-resources "Listing Resources" %}
|
||||
for a comparison.
|
||||
|
||||
|
||||
## Basic Info
|
||||
|
||||
| Resource | Details |
|
||||
|----------|---------|
|
||||
| App title | Title of the app. |
|
||||
| Website URL | Link to the brand or other website related to the app. |
|
||||
| Source code URL | Link to the source code of the app (such as GitHub or BitBucket). |
|
||||
| Support email address | An email address for support issues. If left blank, the developer's account email address will be used. |
|
||||
| Category | A watchapp may be categorized depending on the kind of functionality it offers. Users can browse the appstore by these categories. |
|
||||
| Icons | A large and small icons representing the app. |
|
||||
|
||||
|
||||
## Asset Collections
|
||||
|
||||
An asset collection must be created for each of the platforms that the app
|
||||
supports. These are used to tailor the description and screenshots shown to
|
||||
users browing with a specific platform connected.
|
||||
|
||||
| Resource | Details |
|
||||
|----------|---------|
|
||||
| Description | The details and features of the app. Maximum 1600 characters. |
|
||||
| Screenshots | Screenshots showing off the design and features of the app. Maximum 5 per platform in PNG, GIF, or Animated GIF format. |
|
||||
| Marketing banner | Large image used at the top of a listing in some places, as well as if an app is featured on one of the main pages. |
|
||||
|
||||
|
||||
## Releases
|
||||
|
||||
In addition to the visual assets in an appstore listing, the developer must
|
||||
upload at least one valid release build in the form of a `.pbw` file generated
|
||||
by the Pebble SDK. This is the file that will be distributed to users if they
|
||||
choose to install your app.
|
||||
|
||||
The appstore will automatically select the appropriate version to download based
|
||||
on the SDK version. This is normally the latest release, with the one exception
|
||||
of the latest release built for SDK 2.x (deprecated) distributed to users
|
||||
running a watch firmware less than 3.0. A release is considered valid if the
|
||||
UUID is not in use and the version is greater than all previously published
|
||||
releases.
|
||||
|
||||
|
||||
## Companion Apps
|
||||
|
||||
If your app requires an Android or iOS companion app to function, it can be
|
||||
listed here by providing the name, icon, and URL that users can use to obtain
|
||||
the companion app. When a user install the watchapp, they will be prompted to
|
||||
also download the companion app automatically.
|
||||
|
||||
|
||||
## Timeline
|
||||
|
||||
Developers that require the user of the timeline API will need to click 'Enable
|
||||
timeline' to obtain API keys used for pushing pins. See the
|
||||
{% guide_link pebble-timeline %} guides for more information.
|
||||
|
||||
|
||||
## Promotion
|
||||
|
||||
Once published, the key to growth in an app is through promotion. Aside from
|
||||
users recommending the app to each other, posting on websites such as the
|
||||
[Pebble Forums](https://forums.getpebble.com/categories/watchapp-directory),
|
||||
[Reddit](https://www.reddit.com/r/pebble), and [Twitter](https://twitter.com)
|
||||
can help increase exposure.
|
||||
|
||||
|
||||
## Developer Retreat Video
|
||||
|
||||
Watch the presentation given by Aaron Cannon at the 2016 Developer Retreat to
|
||||
learn more about preparing asset collections for the appstore.
|
||||
|
||||
[EMBED](//www.youtube.com/watch?v=qXmz3eINObU&index=10&list=PLDPHNsf1sb48bgS5oNr8hgFz0pL92XqtO)
|
||||
192
devsite/source/_guides/appstore-publishing/publishing-an-app.md
Normal file
192
devsite/source/_guides/appstore-publishing/publishing-an-app.md
Normal file
|
|
@ -0,0 +1,192 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: Publishing an App
|
||||
description: |
|
||||
How to upload and publish an app in the Pebble appstore.
|
||||
guide_group: appstore-publishing
|
||||
order: 1
|
||||
---
|
||||
|
||||
When an app is ready for publishing, the `.pbw` file needs to be uploaded to the
|
||||
Pebble [Developer Portal](https://dev-portal.getpebble.com/), where a listing is
|
||||
created. Depending on the type of app, different sets of additional resources
|
||||
are required. These resources are then used to generate the listing pages
|
||||
visible to potential users in the Pebble appstore, which is embedded within the Pebble mobile app.
|
||||
|
||||
You can also view the [watchfaces](http://apps.getpebble.com/en_US/watchfaces)
|
||||
and [watchapps](http://apps.getpebble.com/en_US/watchapps) from a desktop
|
||||
computer, as well as perform searches and get shareable links.
|
||||
|
||||
|
||||
## Listing Resources
|
||||
|
||||
The table below gives a summary of which types of resources required by
|
||||
different types of app. Use this to quickly assess how complete assets and
|
||||
resources are before creating the listing.
|
||||
|
||||
| Resource | Watchface | Watchapp | Companion |
|
||||
|----------|-----------|----------|-----------|
|
||||
| Title | Yes | Yes | Yes |
|
||||
| `.pbw` release build | Yes | Yes | - |
|
||||
| Asset collections | Yes | Yes | Yes |
|
||||
| Category | - | Yes | Yes |
|
||||
| Large and small icons | - | Yes | Yes |
|
||||
| Compatible platforms | - | - | Yes |
|
||||
| Android or iOS companion appstore listing | - | - | Yes |
|
||||
|
||||
|
||||
## Publishing a Watchface
|
||||
|
||||
1. After logging in, click 'Add a Watchface'.
|
||||
|
||||
2. Enter the basic details of the watchface, such as the title, source code URL,
|
||||
and support email (if different from the one associated with this developer
|
||||
account):
|
||||
|
||||
|
||||
|
||||
3. Click 'Create' to be taken to the listing page. This page details the status
|
||||
of the listing, including links to subpages, a preview of the public page,
|
||||
and any missing information preventing release.
|
||||
|
||||
|
||||
|
||||
4. The status now says 'Missing: At least one published release'. Click 'Add a
|
||||
release' to upload the `.pbw`, optionally adding release notes:
|
||||
|
||||
|
||||
|
||||
5. Click 'Save'. After reloading the page, make the release public by clicking
|
||||
'Publish' next to the release:
|
||||
|
||||
|
||||
|
||||
6. The status now says 'Missing: A complete X asset collection' for
|
||||
each X supported platform. Click 'Manage Asset Collections', then click
|
||||
'Create' for a supported platform.
|
||||
|
||||
7. Add a description, up to 5 screenshots, and optionally a marketing banner
|
||||
before clicking 'Create Asset Collection'.
|
||||
|
||||
|
||||
|
||||
8. Once all asset collections required have been created, click 'Publish' or
|
||||
'Publish Privately' to make the app available only to those viewing it
|
||||
through the direct link. Note that once made public, an app cannot then be
|
||||
made private.
|
||||
|
||||
9. After publishing, reload the page to get the public appstore link for social
|
||||
sharing, as well as a deep link that can be used to directly open the
|
||||
appstore in the mobile app.
|
||||
|
||||
|
||||
## Publishing a Watchapp
|
||||
|
||||
1. After logging in, click 'Add a Watchapp'.
|
||||
|
||||
2. Enter the basic details of the watchapp, such as the title, source code URL,
|
||||
and support email (if different from the one associated with this developer
|
||||
account):
|
||||
|
||||
|
||||
|
||||
3. Select the most appropriate category for the app, depending on the features
|
||||
it provides:
|
||||
|
||||
|
||||
|
||||
4. Upload the large and small icons representing the app:
|
||||
|
||||
|
||||
|
||||
5. Click 'Create' to be taken to the listing page. This page details the status
|
||||
of the listing, including links to subpages, a preview of the public page,
|
||||
and any missing information preventing release.
|
||||
|
||||
|
||||
|
||||
6. The status now says 'Missing: At least one published release'. Click 'Add a
|
||||
release' to upload the `.pbw`, optionally adding release notes:
|
||||
|
||||
|
||||
|
||||
7. Click 'Save'. After reloading the page, make the release public by clicking
|
||||
'Publish' next to the release:
|
||||
|
||||
|
||||
|
||||
8. The status now says 'Missing: A complete X asset collection' for
|
||||
each X supported platform. Click 'Manage Asset Collections', then click
|
||||
'Create' for a supported platform.
|
||||
|
||||
9. Add a description, up to 5 screenshots, optionally up to three header images,
|
||||
and a marketing banner before clicking 'Create Asset Collection'.
|
||||
|
||||
|
||||
|
||||
10. Once all asset collections required have been created, click 'Publish' or
|
||||
'Publish Privately' to make the app available only to those viewing it
|
||||
through the direct link.
|
||||
|
||||
11. After publishing, reload the page to get the public appstore link for social
|
||||
sharing, as well as a deep link that can be used to directly open the
|
||||
appstore in the mobile app.
|
||||
|
||||
|
||||
## Publishing a Companion App
|
||||
|
||||
> A companion app is one that is written for Pebble, but exists on the Google
|
||||
> Play store, or the Appstore. Adding it to the Pebble appstore allows users to
|
||||
> discover it from the mobile app.
|
||||
|
||||
1. After logging in, click 'Add a Companion App'.
|
||||
|
||||
2. Enter the basic details of the companion app, such as the title, source code
|
||||
URL, and support email (if different from the one associated with this
|
||||
developer account):
|
||||
|
||||
|
||||
|
||||
3. Select the most appropriate category for the app, depending on the features
|
||||
it provides:
|
||||
|
||||
|
||||
|
||||
4. Check a box beside each hardware platform that the companion app supports.
|
||||
For example, it may be a photo viewer app that does not support Aplite.
|
||||
|
||||
5. Upload the large and small icons representing the app:
|
||||
|
||||
|
||||
|
||||
6. Click 'Create' to be taken to the listing page. The status will now read
|
||||
'Missing: At least one iOS or Android application'. Add the companion app
|
||||
with eithr the 'Add Android Companion' or 'Add iOS Companion' buttons (or
|
||||
both!).
|
||||
|
||||
7. Add the companion app's small icon, the name of the other appstore app's
|
||||
name, as well as the direct link to it's location in the appropriate
|
||||
appstore. If it has been compiled with a PebbleKit 3.0, check that box:
|
||||
|
||||
|
||||
|
||||
8. Once the companion appstore link has been added, click 'Publish' or 'Publish
|
||||
Privately' to make the app available only to those viewing it through the
|
||||
direct link.
|
||||
|
||||
9. After publishing, reload the page to get the public appstore link for social
|
||||
sharing, as well as a deep link that can be used to directly open the
|
||||
appstore in the mobile app.
|
||||
56
devsite/source/_guides/appstore-publishing/whitelisting.md
Normal file
56
devsite/source/_guides/appstore-publishing/whitelisting.md
Normal file
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
# Copyright 2025 Google LLC
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
title: iOS App Whitelisting
|
||||
description: |
|
||||
Instructions to iOS developers to get their Pebble apps whitelisted.
|
||||
guide_group: appstore-publishing
|
||||
generate_toc: false
|
||||
order: 4
|
||||
---
|
||||
|
||||
Pebble is part of the Made For iPhone program, a requirement that hardware
|
||||
accessories must meet to interact with iOS apps. If an iOS app uses PebbleKit
|
||||
iOS, it must be whitelisted **before** it can be submitted to the Apple App
|
||||
Store for approval.
|
||||
|
||||
|
||||
## Requirements
|
||||
|
||||
* The iOS companion app must only start communication with a Pebble watch on
|
||||
an explicit action in the UI. It cannot autostart upon connection and it must
|
||||
stop whenever the user stops using it. Refer to the
|
||||
{% guide_link communication/using-pebblekit-ios %} guide for details.
|
||||
|
||||
* `com.getpebble.public` is the only external accessory protocol that can be
|
||||
used by 3rd party apps. Make sure this is listed in the `Info.plist` in the
|
||||
`UISupportedExternalAccessoryProtocols` array.
|
||||
|
||||
* Pebble may request a build of the iOS application. If this happens, the
|
||||
developer will be supplied with UDIDs to add to the provisioning profile.
|
||||
TestFlight/HockeyApp is the recommended way to share builds with Pebble.
|
||||
|
||||
[Whitelist a New App >{center,bg-lightblue,fg-white}](http://pbl.io/whitelist)
|
||||
|
||||
After whitelisting of the new app has been confirmed, add the following
|
||||
information to the "Review Notes" section of the app's Apple app submission:
|
||||
|
||||
<div style="text-align: center;">
|
||||
<strong>MFI PPID 126683-0003</strong>
|
||||
</div>
|
||||
|
||||
> Note: An iOS app does not need to be re-whitelisted every time a new update is
|
||||
> released. However, Pebble reserves the right to remove an application from the
|
||||
> whitelist if it appears that the app no longer meets these requirements.
|
||||
Loading…
Add table
Add a link
Reference in a new issue