Your Bricks Builder website — now a native iOS and Android app, designed with the same Bricks elements you already use. Free preview before you ever ship.
11 native Appress elements drop directly into the Bricks editor — no separate app-builder UI to learn.
Appress was designed against real WordPress sites — and Bricks Builder is one of the platforms it ships first-class support for. Activate the Bricks module in the Appress plugin and the integration shows up directly in your Bricks editor:
Every page, template, query loop, dynamic data field, and custom Bricks element renders in the app exactly as it does on the website.
Notifications, Biometric, QR Login, QR Scanner, Apple Login, Account Deletion, Menu Toggle, Back Button, Status Bar Height, Dismiss First Launch, TranslatePress Switcher — drag directly onto your Bricks canvas.
Native “Appress” condition group: “In Appress app (any platform)”, “In Appress app (Android)”, “In Appress app (iOS)”, and “Appress app id matches” — hide or show any element per surface, with Bricks’ own conditional system.
Build app screens using the Bricks editor, your existing templates, and your custom elements. No proprietary “app builder” UI to learn.
Publish a new post, change a price, update a query loop on Bricks — it’s in the app on the next tap. No re-submission for content updates.
Real Apple Push on iOS, Firebase Cloud Messaging on Android. Trigger from any WordPress hook or Uncanny Automator workflow.
Apple Login, Google Sign-In, QR Login, QR Scanner, and Biometric — all available as Bricks elements you drop on your sign-in templates.
Account Deletion + Apple Login elements pass App Store review on first submission. No legal scrambles, no custom code.
Menu Toggle, Back Button, Status Bar Height, Dismiss First Launch — the native scaffolding your mobile-only Bricks templates need.
Multilingual Bricks sites get the language switcher as a native Bricks element — first-class integration, not a workaround.
Need the technical reference? The Bricks Builder integration docs cover every element, Display Condition, hook, and configuration option.
Install the free Appress plugin on the same WordPress install your Bricks site runs on. Toggle the Bricks module from the Appress integrations page. The “Appress” category appears in your Bricks editor panel immediately. About 5 minutes.
Open Bricks editor, drag elements from the Appress group onto your templates. Configure Display Conditions to route app-only screens. Wire up biometric login, push opt-in, and account deletion with point-and-click. Typically 1–2 hours for a complete app.
Install the Appress Preview companion app on your phone, scan a QR code, and your Bricks-designed app boots instantly — no build server, no submission required. When the design feels right, trigger the production build and submit to App Store Connect + Google Play Console. Self-serve customers usually publish within 7 days.
| Capability | Appress | PWA | Custom-built | Generic app builder |
|---|---|---|---|---|
| Real native iOS + Android app in stores | ✓ | ✗ | ✓ | ✓ |
| Built specifically for Bricks Builder | ✓ | ✗ | rebuild | ✗ |
| Native Appress elements inside the Bricks editor | ✓ 11 elements | ✗ | ✗ | ✗ |
| Bricks Display Conditions for app / iOS / Android / app id | ✓ | ✗ | rebuild | ✗ |
| Native push notifications (APNs + FCM) | ✓ | ⚠ iOS limited | ✓ | partial |
| Biometric login (Face ID / Touch ID / fingerprint) | ✓ | ✗ | ✓ | partial |
| Sign in with QR code | ✓ | ✗ | rare | ✗ |
| App Store-ready Account Deletion + Apple Login | ✓ as Bricks elements | ✗ | custom code | partial |
| Free preview before purchase | ✓ | ✗ | ✗ | ✗ |
| Content updates without app-store re-submission | ✓ instant | ✓ instant | ✗ manual rebuild | ✗ manual rebuild |
| Time to first build | minutes | days | 3–6 months | weeks |
| Year-one cost | low, pay per ship | very low | $30k–$150k+ | $19–$799/mo |
Generic app builders don’t understand Bricks — they ignore your query loops, dynamic data, and custom elements. Custom development rebuilds your site at huge cost. Appress hits the sweet spot: native Bricks elements, real App Store-ready output, free to evaluate.
The Appress Bricks integration registers a full “Appress” element category in your Bricks editor: Notifications opt-in, Biometric login button, QR Login + QR Scanner, Apple Login, Account Deletion (App Store-compliant), Menu Toggle, Back Button, Status Bar Height spacer, Dismiss First Launch, and TranslatePress Switcher. Drag, configure, save — your sign-in template, your account page, your app chrome all use real Bricks elements, not embeds or shortcodes.
Appress adds four Display Conditions to Bricks’ own conditional system: “In Appress app (any platform)”, “In Appress app (Android)”, “In Appress app (iOS)”, and “Appress app id matches” (for multi-app sites). Build a single Bricks template, hide a sidebar on the app, show a download banner only on web, swap a header per platform — all with Bricks’ native conditions UI.
Real Apple Push (APNs) on iOS, Firebase Cloud Messaging on Android — the same channel Instagram and Uber use. Trigger from any WordPress event, Uncanny Automator workflow, or custom hook. Drop the Notifications element from the Appress group into a Bricks template and the opt-in UI is there.
Schedule and send push campaigns from the Appress dashboard. Target by app, by platform (iOS vs Android), by user segment. Read-tracking and delivery stats built in. Run marketing campaigns the same way you run email — but with iOS-grade delivery.
Publish a new post, change a price, update a query loop on Bricks — it’s in the app on the next tap. Compare to custom-built native apps where every content change waits 3–7 days for Apple App Review.
Sign up for free at my.appress.app and connect your Bricks site. Configure your branding, drop Appress elements onto your Bricks templates, and see your configured app live on your phone via the Appress Preview app — no build, no commit.
Open the Appress Preview companion app on your phone, scan the QR shown on my.appress.app, and your Bricks-designed app boots instantly. Zero card, zero submission queue, zero commitment.
iOS and Android builds, push infrastructure (APNs + FCM), all Bricks Builder elements + Display Conditions, App Store-ready compliance, white-glove submission help.
If your Bricks Builder site has any of: a sign-in flow, a custom query loop, an account page, or active return users — Appress was built for you.
Can you build a native mobile app for a Bricks Builder WordPress site?
Yes. Appress turns Bricks Builder-powered WordPress sites into real native iOS and Android apps that ship to the App Store and Google Play. The Appress plugin registers 11 native elements and 4 Display Conditions directly inside the Bricks editor.
Does Appress preserve my Bricks Builder design?
Yes. Your Bricks templates, custom elements, query loops, and dynamic data render in the app exactly as on the website. No design rebuild, no parallel UI system to maintain.
What Appress elements are available in the Bricks editor?
Eleven elements in a dedicated Appress category: Notifications opt-in, Biometric login, QR Login, QR Scanner, Apple Login, Account Deletion (App Store-compliant), Menu Toggle, Back Button, Status Bar Height, Dismiss First Launch, and TranslatePress Switcher.
Can I show or hide elements per platform — web vs app vs iOS vs Android — inside Bricks?
Yes. Appress adds four Display Conditions to Bricks’ own conditional system: “In Appress app (any platform)”, “In Appress app (Android)”, “In Appress app (iOS)”, and “Appress app id matches”. Use them on any element with Bricks’ native conditions UI.
What sign-in methods does the app support?
Email and password (your existing WordPress login), Apple Login, Google Sign-In, Sign in with QR code (scan from desktop, signed in on phone instantly), and biometric return-login with Face ID, Touch ID, or Android fingerprint. All available as Bricks elements.
Does Appress support push notifications on Bricks sites?
Yes. Real Apple Push (APNs) on iOS and Firebase Cloud Messaging on Android. Drop the Notifications element from the Appress group onto a Bricks template to surface the opt-in UI. Trigger pushes from any WordPress hook or Uncanny Automator workflow.
Will my Bricks Builder query loops and dynamic data work in the app?
Yes. Every Bricks query loop, dynamic data field, and custom element renders in the app as it does on the website. No mapping or rebuilding required.
Does the app handle App Store compliance — Account Deletion, Apple Login?
Yes. Account Deletion and Apple Login ship as native Bricks elements you drop onto your account templates. Designed to pass App Store review on first submission.
Is the app multilingual?
Yes. Sites running TranslatePress get a first-class native integration — the TranslatePress Switcher is available as a Bricks element you place anywhere.
How long does it take to ship a Bricks Builder app to the App Store?
Inside Bricks, you can wire up a complete app in an afternoon. After hitting build, Apple’s review queue runs 24–72 hours for most apps; Google Play is usually same-day to 48 hours. Agencies shipping client apps on Bricks routinely list within 5 business days of plugin install.
Do I need to rebuild my Bricks Builder site to use Appress?
No. Install the Appress plugin, activate the Bricks module, drop Appress elements onto your existing Bricks templates, preview, and ship. Your Bricks site stays exactly as it is.
How much does a Bricks Builder mobile app with Appress cost?
Appress doesn’t charge a monthly subscription. The Bricks Builder integration and the live preview on your phone are free; you only pay a per-build fee at the moment you submit the production app to App Store Connect or Google Play Console. Current tier breakdown is on the pricing page.
Do I need to resubmit to the App Store every time I update content on a Bricks site?
No. Content changes — new posts, price updates, new query loop entries, anything you publish on WordPress — appear in the app instantly on the next tap.
Agencies often work across multiple WordPress stacks. Here’s how Appress integrates with the other major page builders and themes you might encounter:
For agencies building directory or marketplace sites, Voxel ships pre-built UI for listings and bookings that would take months to recreate in Bricks. Use the Voxel integration when directory features matter more than custom design.
If a client demands Avada theme (still 750k+ install base), the Avada Builder integration gives you the same Appress capabilities without forcing a stack migration.
Bricks vs Elementor is a long debate. If your client team standardized on Elementor Pro before you joined, the Elementor integration matches what they already know.
For Bricks sites layered with WooCommerce, the WooCommerce integration adds cart indicators, push on order events, and Apple Pay/Google Pay checkout on top of your Bricks build.
Overview of every theme/builder integration — Voxel, Bricks Builder, Avada theme, Elementor, WooCommerce, stock WordPress.
Bricks Builder is the WordPress designer’s tool of choice for a reason. Appress extends that same precision to iOS and Android — same editor, same elements, real native delivery.