A walkthrough of design concepts for importing RSS feeds and bulk posts into Subwave, making platform migration seamless for creators.
The ability to import bulk posts from other platforms solves a real pain point. Creators shouldn't have to choose between their existing content library and trying a new platform. Whether it's moving from YouTube, a blog, or another content platform, having a smooth import process removes friction and gets creators up and running faster.
We explored a couple of entry points for this feature, both living naturally within the existing post management flow.
Option One: The Overflow Menu
In the first approach, when you're in your post view and select your channel, there's an additional option for "Import" sitting in the overflow menu. Tap that, and you get a context menu asking you to choose between uploading a file or pasting a URL.
This flexibility matters because RSS data can come in different formats—sometimes you're downloading an XML file, other times you have a feed URL. And here's where it gets interesting: you're not limited to bulk imports. If you just want to grab a single YouTube video or one specific post from another platform, you can paste that individual URL and import just that one piece of content.
If you were to import an RSS feed it would create multiple different draft posts, and if you were to open that draft post you would see just your video or content.
Option Two: Direct From New Post
The second sketch puts the import option right at the post creation level. When you tap "New Post," you'd see options to either create a new post from scratch or import from an RSS feed. It's a more direct path for creators who know they want to bring content in rather than create something new.
Once you've selected your import method and pasted your URL or uploaded your file, you hit a loading state while the system processes everything. Then you land directly in the Drafts tab.
This is where the design gets smart about not overwhelming the system or the creator.
Each imported piece of content becomes its own individual draft post. If you're importing an entire RSS feed with fifty posts, you'll see fifty separate drafts waiting for you. They're not automatically published, and importantly, they're not automatically processed through Subwave's AI features yet.
When you open an individual draft, you'll see your video or content, but we're not automatically generating articles or versions for bulk imports. Why? Because running AI processing on potentially dozens of posts simultaneously could take too much time and resources.
Instead, there's an action button right there: "Generate article" or "Get versions." You decide when to process each piece of content, giving you control over the workflow and spreading out the computational load.
For now, the design assumes you'll publish each article individually as you review and finalize it. There's potential for bulk publishing down the road, but starting with individual publishing makes sense—it's more deliberate, and it ensures creators are actually reviewing their content before it goes live rather than blindly pushing everything out at once.
The sketches account for different import sources—XML files, RSS feed URLs, individual content links. This flexibility recognizes that creators' content lives in different formats across different platforms, and the import tool needs to handle that variety gracefully.
The decision to delay AI processing until the creator explicitly requests it is a practical one. It prevents the system from getting bogged down trying to process a massive batch import all at once, and it gives creators agency over which posts get the full treatment.
Features like this might not generate buzz the way new AI capabilities do, but they're crucial for platform growth. Reducing the friction of migration means more creators are willing to give Subwave a try without feeling like they're abandoning their existing content library.
Getting creators' content onto the platform faster means they can start using and benefiting from Subwave's other features sooner. It's the kind of foundational feature that enables everything else.
