Canny does not have an iOS SDK. It does not have an Android SDK.
What they ship for mobile is a WebView pointed at webview.canny.io, and it only works if you implement SSO. Their own docs say that. Their own board still has an open request titled “Native Mobile Widget” with 100+ votes.
Featurebase and Nolt get the same question. The answers are different, and both still leave you without a native voting board inside the binary.
This is the mobile cut. The PM-suite comparison lives here: Canny vs Featurebase vs Productboard. Do not use that post to decide what goes in Xcode.
Quick answer
| Tool | What “mobile” actually is | Native iOS SDK | Native Android SDK | Users vote without a login wall |
|---|---|---|---|---|
| Canny | WKWebView / Android WebView + boardToken. SSO required | No | No | No — SSO is mandatory for the mobile widget |
| Featurebase | JS widget on the web. Separate admin app for your team | No | No | Portal in a WebView |
| Nolt | Not officially supported in apps. Community WebView hacks | No | No | Fragile (cookies, localStorage, popup auth) |
| WishKit | Real SwiftUI/UIKit SDK | Yes | No | Yes |
| FeedbackJar | Swift + Kotlin + RN + Flutter | Yes | Yes | Yes (guest vote via install id) |
If the job is “users tap Feature requests in Settings and vote,” three of those rows are a website wearing an app costume.
Canny: a WebView they call a widget
From Canny’s install docs:
- Create a WebView (
WKWebViewon iOS). - Load
https://webview.canny.io?boardToken=...&ssoToken=. - Generate the SSO token on your server.
They also write: the mobile widget only works with SSO. No SSO → send people to your-company.canny.io in the browser.
That is a product decision, not a missing doc page. A native SDK would not need a JWT minted on your backend before the screen can render.
What you inherit:
- Theme is Canny’s page, not your Settings list
- Cold start is a network round-trip to HTML/CSS/JS
- Offline = blank
- Device metadata is a user-agent string unless you stuff extra fields through Identify
- App Review is usually fine. Completion rate is not
Canny’s public board has asked for a native widget for years. The official response was “we made the WebView easier” and they left the request open. That is the current state.
Canny is still a good website board. Pricing and roadmap story: Canny alternative.
Featurebase: “mobile app” ≠ SDK
Featurebase shipped iOS and Android apps. Those apps are for you — support inbox, AI replies, notifications in your pocket.
That is not an SDK you drop into your product so your users vote.
What Featurebase gives end users in an app:
- JavaScript SDK (
featurebase-js) on the web - “Featurebase in mobile apps” = embed the portal in a WebView with auto sign-in
Same WebView shape as Canny. Different dashboard. Still HTML.
If you want changelog + surveys + help center on a marketing site, Featurebase is in the conversation. If you want FeedbackJarBoard() on a Settings row, it is not. Featurebase alternative.
Nolt: unsupported, with a warning
Nolt’s help center is blunt: widgets are not officially supported in Android or iOS apps.
Workarounds they list:
- WebView with
DOMStorage/ localStorage enabled - SSO + JWT, because widget auth opens a new browser window and that breaks WebViews
- Third-party cookie errors; an undocumented
skipTests: trueflag
“Many users have made it work” is not an SDK. It is a support ticket you will file after the first OS WebView change.
Skip Nolt for mobile. Use it on the site if you already have it.
Why the WebView keeps getting sold as an SDK
“SDK” in Canny’s help center means a JavaScript snippet plus Identify. That language leaks into mobile pages.
Three tests. Fail one and you do not have a mobile SDK:
- The UI is SwiftUI / UIKit / Views / Compose — not a URL.
- Submit works without standing up SSO on day one.
- The report carries app version, OS, model — not only a browser UA.
Canny fails 1 and 2. Featurebase fails 1. Nolt fails all three officially.
WishKit passes on Apple and stops. That is the WishKit Android problem, not this one.
What you should do instead
Web SaaS, mobile is a companion.
Keep Canny or Featurebase. Link out. Do not fight the WebView.
iOS-only, you want native.
WishKit or FeedbackJar. WishKit alternative if Play is even a maybe.
iOS + Android, one vote count.
A Kotlin artifact and a Swift package that share a board. FeedbackJar is built for that. Guest votes do not require SSO. Metadata is OS, model, screen, app version, locale.
You already pay for Canny.
Import the posts (Canny import if you switch), or run Canny on the web and a native board in the app. Two backlogs is the cost of delaying that decision.
Trial is 7 days, no card, SDKs on every plan: feedbackjar.com.
FAQ
Does Canny have an iOS SDK in 2026?
No. Mobile install is a WebView + board token + SSO token.
Can I use Canny without SSO in an app?
Not the mobile widget. Docs send those users to the hosted Canny site.
Is Featurebase Mobile the feedback SDK?
No. It is an admin client for the support inbox.
Will a WebView fail App Review / Play review?
Usually no. Users failing to vote because of a login wall is the actual loss.
I already wrote the Canny vs Featurebase blog post. Is this a duplicate?
No. That post is for PMs choosing a suite. This one is for the person holding Android Studio asking “what package do I add?”
Bottom line
Ask the vendor for the Maven coordinate and the SPM URL.
If the answer is a WebView URL and a JWT, you do not have a mobile SDK. You have a website with extra steps.
Start a 7-day trial if you want the Settings-row version on both stores.