Custom Page (CMS) Feature

S
Swiftspeed Team
Updated April 27, 20264 min read

What is the Custom Page Feature?

The Custom Page feature is a block-based content builder that turns a mobile app into a mini CMS. Each page is built from blocks: text, image, image gallery, slider, video, audio, file download, source code, and more. Drag blocks into the page, fill in the content, and the native app renders it as a polished mobile page.

Custom Pages are how you ship branded marketing content (Our Story, FAQ, Terms of Service), promotional landing pages, info hubs, blog-like article pages, anywhere the dedicated features (Audio, Wallpaper, Form) do not fit. One Custom Page feature can contain many pages, organised under categories.

Adding the Custom Page Feature to Your Mobile App

Click the edit pencil on the mobile app you want to add custom content pages to.

Swiftspeed dashboard with the Demo App card highlighted

Click Features in the top bar.

App Editor with the Features tab highlighted

Find the Custom Page card and click the + button. The CMS feature is added to the app, ready for you to build pages.

Add a Page list with the Custom Page card highlighted

The Editor: Three Tabs

The Custom Page editor has three tabs:

The Pages tab is the main workspace. Add Category, then Add Page inside it. Each page opens its own block editor where you drag content blocks (text, image, slider, video, etc.) into a vertical stack.

Custom Page editor on the Pages tab showing categories and the page builder
  • Appearance: theme + custom colors that style every page in this feature.
  • Structure: layout settings (single-page mode vs. multi-page list, navigation pattern, header behavior).
  • Pages: the actual page builder. Add categories, add pages inside each category, drag blocks into each page.

Block Types

Inside any page, you stack blocks top-to-bottom. Available block types:

  • Text: paragraphs with optional rich formatting (bold, italic, links). Single-column or two-column layouts.
  • Image: a single image with optional caption.
  • Image gallery: a grid of images that opens a full-screen lightbox on tap.
  • Slider: horizontal swipeable image carousel. Each slide can have a caption + tap action.
  • Video (link): any direct video URL (mp4 hosted on your CDN).
  • Video (YouTube): paste a YouTube URL, the native page embeds the player.
  • Video (Podcast / Vimeo): same pattern for other hosts.
  • Audio: a single audio file with native playback controls.
  • Source code (HTML): arbitrary HTML/CSS/JS embedded inside the page (similar to the standalone Source Code feature, but inline as one block).
  • File / Download: link to a downloadable file (PDF, ZIP, etc.) with file size + type display.

Blocks can be reordered by dragging the handle on the left of each block. Each block type has its own inline editor that opens when you click into it.

Live Preview

Here is how a Custom Page renders inside a real phone (showing the empty state for a feature with no pages added yet, customers replace this with their own content):

The native page list. Once you add pages in the editor, they appear here organised by category. Tapping any page opens it in a full-screen native view that renders the blocks you stacked.

iPhone-style phone frame rendering the Custom Page feature in its initial state

Tips and Best Practices

  • Categories matter for navigation. When you have many pages, group them into 2-4 categories so the native page list reads like a tidy menu rather than a 30-item scroll.
  • Image blocks: 1200px wide is the sweet spot. Anything bigger inflates load time without visible quality gain on phones. JPG at 80-85 quality is usually invisible from native ones.
  • Slider blocks need same-aspect-ratio images. Mixing portrait + landscape inside one slider creates jumpy heights on swipe. Pick one orientation per slider.
  • YouTube embeds work even when the user has no YouTube account. The native page hosts the player without requiring sign-in.
  • The Source Code block is one inline div. It runs in the same webview as the surrounding page. Avoid redirecting or replacing window.location, it would crash the page.
  • File blocks should pre-declare size. Users on cellular avoid downloading anything labeled as 50+ MB. The block reads file size from the URL automatically; if it can't (server doesn't expose Content-Length), set it manually in the block options.
  • Custom Pages are the right place for legal text. Privacy policy, terms, accessibility statement. The text block handles long-form content cleanly without needing external hosting.