Capture feedback in the moment
Use the SDK when users should not leave the app to report a bug or request a feature. A settings link, help screen, or contextual feedback button can open the Portal directly.
Gleam's iOS SDK gives Swift teams two paths: present the official hosted Portal, or use SDK APIs to build a custom feedback board, announcement feed, and notification center in SwiftUI or UIKit.
Add the Swift package, pass the user context you already have, then present the official Portal or render feedback, announcements, notifications, and preferences in your own UI.
SwiftUI or UIKit entry point
Portal preset or SDK APIs
Feedback, updates, and inbox
The problem
Asking users to leave the app, open a forum, or sign in again kills the moment when feedback is most useful. By the time they reach a web form, the context is gone.
The solution
Drop Gleam into your iOS project and choose the surface that fits your app. Use the Portal preset for the full Gleam experience, or call the feedback, announcements, notification, preference, and push APIs from your own native UI.
Capabilities
Each product area is designed to stay lightweight enough for a small team, while keeping the data structured enough for automation, reporting, and agent-assisted work.
Use cases
These are the situations where the feature should be visible to users or connected to an internal product workflow.
Use the SDK when users should not leave the app to report a bug or request a feature. A settings link, help screen, or contextual feedback button can open the Portal directly.
If the feedback experience should match the rest of your app, fetch boards and posts with the SDK, render them in SwiftUI or UIKit, and submit posts, votes, and comments through the same no-login session.
Use announcement and notification APIs to show a custom in-app update feed, unread notification state, and preference controls without sending users to a separate web view.
Anonymous sessions help apps collect useful feedback before account creation. Signed identity can be added later when the app knows the current user and wants profile-aware follow-up.
Swift teams can combine Portal UI, notification polling, push preferences, and APNs device token registration so feedback does not end at submission.
Workflow
Add the Swift package and configure your Gleam project key.
Use the Portal preset, native feedback APIs, or custom announcement and notification APIs.
Keep anonymous users, signed identity, preferences, APNs, and routed notification URLs on the same session.
Implementation
Gleam is designed to start small, but each feature still has a few product decisions worth making before inviting users.
Initialize Gleam once with the project ID and SDK key. Present the Portal when you want Gleam's complete H5 flow, or call SDK APIs when your app owns the feedback, announcement, and notification screens.
Custom feedback and notification screens should still call start() first. That preserves no-login anonymous users, signed identity upgrades, project headers, and the same moderation and follow-up pipeline as the Portal.
The iOS app should never generate identity tokens. Your backend signs short-lived HS256 tokens after authenticating the user, then the SDK exchanges that token for a Gleam session.
The quickest launch path is Portal UI first. Add APNs registration after the session, identity, notification permission, and deep-link routing have been tested in the host app.
Outcomes
More features