A full-screen video feed for Android,
without building the player.
A smooth, swipeable video feed looks simple and takes months to get right. FyreMemories ships a production-ready full-screen feed with preloading, caching, auto-advance, and analytics, and fills it with memories built from your users’ own media.
Why a video feed is harder than it looks
Playing one video with ExoPlayer is easy. Playing a feed of videos that start before the user taps, survive fast swipes, recover from network drops, and behave the same across Android devices is not. Most of the effort sits in the last 20% of the work.
- Prefetch and caching so the next video is ready before the swipe ends.
- Player lifecycle across fragments, rotation, and backgrounding without leaks.
- Seek and auto-advance that stay correct under rapid input.
- Device fragmentation on chipsets, OEM skins, and Android versions QA did not cover.
- Analytics that count views, completions, and replays accurately across sessions.
What the FyreMemories feed includes
Open the feed as an Activity with FyreMemories.openFeed(context) or embed MemoriesFeedFragment in your own screen. The feed handles playback, buffering, and the action chrome for you.
- Vertical or horizontal swipe navigation with auto-advance.
- A seek bar and play, pause, and replay controls.
- Like, save, share, and download actions, each with listener hooks.
- Customizable share intents and download locations through providers.
- Per-user, on-disk caching that keeps accounts isolated on shared devices.
Analytics built into the feed
Every feed page records VIEWED, PLAYED, PAUSED, COMPLETED, REPLAYED, LIKED, SHARED, DOWNLOADED, and ERRORED events. Events are batched and sent automatically, and you can log custom events, filter which events are sent, honor user consent, or route events to your own analytics pipeline with a custom dispatcher.
Build vs. buy
If short-form video is your core product, building your own feed can make sense. If the feed exists to bring users back to their own content, an SDK lets your engineers spend those months on the parts of the product only your team can build.
Frequently asked questions
Does the feed use ExoPlayer?
Yes. The SDK wraps Media3 (ExoPlayer) with its own preloading and cache layer, so you do not add or configure a player yourself.
Can I embed the feed inside my own screen?
Yes. Use MemoriesFeedFragment to embed the feed, or MemoriesFeedActivity through FyreMemories.openFeed() for a full-screen experience.
Can I build my own feed UI instead?
Yes. MemoriesRepository exposes memory data as a Kotlin Flow, so you can render a custom feed and still use FyreMemories for data, caching, and analytics.
Does it work from Java?
Yes. Public methods are annotated with @JvmStatic and @JvmOverloads so the SDK is usable from Java and Kotlin.