Authentication

Feddy is anonymous-first. Once you call Feddy.configure(...), every submission and vote is attributed to a per-install anonymous token (e.g. anon_a1b2c3d4) persisted via AsyncStorage. That works fine for apps without sign-in.

If your app does have accounts, call Feddy.identify(...) after sign-in and Feddy reconciles previous anonymous activity to the real user ID — nothing is lost.

Identify after sign-in

Call identify(...) once your app knows who the user is. Like other writes, it's synchronous, fire-and-forget, and never throws.

Feddy.identify({ userId: 'user_abc' });

Feddy.identify({
  userId: 'user_abc',
  email: 'alice@example.com',
});

Feddy.identify({
  userId: 'user_abc',
  email: 'alice@example.com',
  displayName: 'Alice Chen',
  avatarUrl: 'https://example.com/avatar.jpg',
});

Only userId is required. email, displayName, and avatarUrl are optional — pass them as you collect them.

Anonymous reconciliation

If a user submits feedback before signing in, then signs in later, the flow looks like this:

Feddy.configure({ apiKey: 'fed_xxxxxxxxxxxx' });
Feddy.submitRequest({ title: 'Add dark mode' });
// Attributed to anon_a1b2c3d4

Feddy.identify({
  userId: 'user_abc',
  email: 'alice@example.com',
});
// Server links anon_a1b2c3d4 → user_abc

Feddy.submitRequest({ title: 'Allow custom themes' });
// Attributed directly to user_abc

Logout

Clear the configured user and any cached state when the user signs out:

Feddy.reset();

reset() clears the last identified user, manual subscription override, and cached server capabilities. The anonymous token is intentionally preserved so any feedback the user submitted before login still links correctly if they sign in again.

After reset(), subsequent writes attribute to the same anonymous token until you call identify(...) again.

What's next