How It Works

Fidbek follows the same conceptual flow on React Native, Expo, iOS, Android, and Flutter:

1. SDK is configured during app startup.
2. User triggers feedback (shake or manual action).
3. Category selection and feedback UI are presented.
4. Report payload is sent to the fixed SDK endpoint.

Payload shape (high level)

• token: identifies workspace/project context
• category: for example bug or improvement
• message: user feedback body
• occurrence_frequency: optional bug frequency signal (first_time, few_times, etc.)
• device/app info: execution context metadata
• locale: device locale metadata
• occurred_at: event timestamp

Endpoint

https://api.fidbek.dev/v1/sdk/reports

Trigger strategy

• Keep shake trigger enabled for quick internal QA access.
• Add a manual trigger entry in Settings/Help for production UX clarity.
• Disable shake if your app interaction model conflicts with motion gestures.

Localization strategy

• SDK ships with built-in UI translations for English (en), Turkish (tr), Spanish (es), French (fr), German (de), Portuguese (pt), Arabic (ar), Hindi (hi), Japanese (ja), and Simplified Chinese (zh-Hans / zh-CN).
• If device locale is not supported, SDK falls back to English automatically.

Performance notes

• SDK runtime is mostly idle until user triggers the flow.
• Network call is performed only during report submission.
• No continuous heavy background processing is required.