The in-app stories SDK
built from your users’ own moments.
FyreMemories gives your Android app a stories experience users already know: a row of story rings and a full-screen, swipeable feed. Unlike stories tools built for marketing teams, the content comes from the photos and videos your users already upload, so every story is personal.
What is an in-app stories SDK?
An in-app stories SDK is a library that adds the stories format (tappable rings at the top of a screen that open a full-screen, auto-advancing viewer) to your own mobile app, without building the UI, video player, caching, and analytics from scratch.
Most stories SDKs are publishing tools. A marketing or editorial team creates stories in a dashboard, and the SDK shows the same stories to many users. FyreMemories takes a different approach: it builds stories automatically from each user’s own photos and videos, so the format drives return visits instead of only promotions.
What you get out of the box
The SDK ships two UI surfaces and a headless data layer. You can use one surface, both, or only the data layer with your own UI.
- MemoriesCarouselView: a horizontal strip of story rings (CIRCLE mode) or card tiles (STORIES mode). Drop it into any layout and bind it with one call.
- Full-screen feed: an auto-playing, swipeable viewer with a seek bar and like, save, share, and download actions. Open it from anywhere with FyreMemories.openFeed().
- MemoriesRepository: a reactive Kotlin Flow of memory items for teams who want to render a fully custom stories UI.
- Analytics: views, plays, completions, replays, likes, shares, and downloads are recorded and batched automatically.
How to add stories to an Android app in three steps
Integration follows the same flow for every team. The full walkthrough is in the SDK docs.
- 1
Add the dependency
Add io.fyre.memories:fyre-memories-sdk from Maven Central. Your module needs minSdk 24, compileSdk 35, and a Java 17 toolchain.
- 2
Initialize after sign-in
Call FyreMemories.init() once Firebase Authentication has a signed-in user (any provider, including anonymous).
- 3
Render the stories
Place MemoriesCarouselView in your layout and bind it, or call FyreMemories.openFeed(context) to open the full-screen viewer.
implementation("io.fyre.memories:fyre-memories-sdk:<latest-version>")Built to match your brand
Ring size, spacing, ring colors, headers, fonts, transitions, and the actions shown in the feed are all configurable. Customization updates are reactive, so live views re-render without restarting the screen.
Need to gate content behind a paywall, show an ad, or require login before a story opens? A MemoryClickInterceptor lets you run your own logic before the feed opens.
Frequently asked questions
Is FyreMemories a Storyly or InAppStory alternative?
It solves a different problem. Storyly and InAppStory are built for teams that publish curated stories to many users. FyreMemories generates personal stories for each user from the media they already uploaded. Some apps use both.
Which platforms does the stories SDK support?
The Android SDK is available today and supports Android 7.0 (API 24) and above. Other platform SDKs run on the same processing engine.
Can I use only the story carousel?
Yes. The carousel and the full-screen feed are independent components. Use one, the other, or both.
Do I need my own video player?
No. Playback, caching, and prefetching are handled by the SDK using Media3 (ExoPlayer).
How much does it cost?
The free plan covers up to 1,000 monthly active users. See the pricing page for paid and pay-as-you-go options.