Pebble Developer Account - one-time migration

General Discussion
1

Today I got an email from info@repebble.com saying

We’re doing a one-time migration to switch from email-based auth to Google/Github/Apple OAuth. This will match the upcoming sign-in options in Pebble mobile app

Actually, I don’t like my accounts bound to Google, Apple, or Github.

Why not work with a modern standard like WebAuthn ( WebAuthn - Wikipedia )? Passkeys work now on most devices and can be stored in password managers like 1Password.

2 Likes
2

We figured if you use Pebble on iOS or Android, you must have a Google or Apple account. Github is also very popular.

I’m not sure if Firebase (our identity provider) supports webauthn yet. But I’ll check it out!

3 Likes
3

Thank you, at least for Android devices there are alternatives not requiring a Google account: GrapheneOS, CalyxOS, /e/OS, LineageOS, Replicant, DivestOS, OmniROM, crDroid, Pixel Experience, ArrowOS, Havoc-OS, Bliss OS…

Whenever I have the choice between Google/Apple log in and email I choose email with unique email address to avoid the aggregation of account data.

3 Likes
4

A lot of us do not want to use identifiable emails. Please look into alternatives. Pebble should stand out on privacy.

3 Likes
5

You’re free to use a non-identifiable email address if you like, but it must be connected to Google/Apple/Github.

2 Likes
6

This worked perfectly for me. I was able to use this to switch to my preferred email address for developer stuff, too. Nice work! :flexed_biceps:

1 Like
7

I have to agree - Pebble is attractive to me as a product as it keeps me in control of my data. Requiring a google / apple / GitHub(microsoft) account runs counter to this. I would prefer an alternate option to an account on

1 Like
8

Let me start out that I already use the Google or Github method of signing in especially because I do not like creating 101 accounts.

What I miss is the reason why Pebble stops supporting the email+password way of signing in. If its just

then why remove it? Its good to have options. I can think of reasons but they aren’t mentioned here (perhaps in the email, I didn’t receive it).

—

Now let me take the other side. People talk about having alternatives but other than WebAuthn none are suggested. If its big-tech concerns… I don’t see any real alternatives here: List of OAuth providers - Wikipedia

And WebAuthn/passkeys doesn’t seem that common place. An frequently mentioned disadvantage seems to be the complexity of implementation.

1 Like
9

The Pebble appstore developer site uses the same sign-in as the main Pebble app. We don’t want the main Pebble app to use username/password for sign-in because we don’t want to have to do customer support for people who forget their password or lose access to their email. Unfortunately, that means the Pebble appstore developer site also cannot use email and password as a sign in. Sorry.

1 Like