How It Works

Fidbek follows the same conceptual flow on 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
• device/app info: execution context metadata
• occurred_at: event timestamp

Endpoint

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

Trigger strategy

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

Performance notes

• The SDK is mostly idle until triggered.
• Network call is performed only during report submission.
• No continuous heavy background processing is required.