r/ionic • u/shane-ionic • Aug 19 '26
Announcing Ionic Framework 9
r/ionic • u/Massive_Educator_CG • Jan 28 '23
r/ionic • u/chazzamoo • Jun 16 '21
r/ionic • u/Massive_Educator_CG • Oct 09 '22
r/ionic • u/brandy-ionic • Jul 31 '25
Ionic Framework 8.7 is out, featuring new Reorder events for fine-grained control, comprehensive CSS utility classes for responsive layouts, and an upgrade to Ionicons v8 that improves Safari compatibility.
Key highlights:
New Reorder events (ionReorderStart, ionReorderMove, ionReorderEnd) for better drag-and-drop control
Comprehensive CSS utility classes for display and flexbox layouts
Ionicons v8 with improved Safari SVG rendering
Angular IonModalToken for easier modal injection
r/ionic • u/ultracryptocurrency • Nov 16 '20
Visit coding.community to check it out. It was built with react and ionic. Please leave me feedback if possible 🙏
r/ionic • u/rdlabo • Sep 18 '26
I’ve been working on an iOS 27 theme for Ionic for a while, and it just reached 1.0.0 today.
https://github.com/rdlabo-dev/ionic-theme-ios27
This actually started with my iOS 26 theme. While building it, the Ionic team was really supportive in expanding the theming APIs needed for this kind of work.
Things like the new Host Classes and Shadow Parts added in Ionic 8.8 made a big difference. They make it much easier to build a custom theme without fighting against Ionic itself.
For the iOS 27 version, I’ve been obsessing over the little details to make it feel as close to native iOS as possible.
I’ve also been experimenting with something called Native UI Shell.

Instead of reproducing everything with CSS, it can take selected Ionic UI elements such as ion-toolbar, ion-tab-bar, and ion-fab-button and render them through the native UIKit layer.
It’s still experimental, so I’m testing it in real apps before considering that part stable, but the results have been pretty interesting so far.
I’d be really interested to hear what other Ionic developers think about this approach, especially where you’d draw the line between CSS theming and native UI.
I also have themes for iOS 26 and Material Design 3, but I’ll avoid turning this into a wall of links 😄
Happy to share the repo/package if anyone wants to take a look.
r/ionic • u/brandy-ionic • Mar 06 '26
Ionic Framework 8.8 is here! This release brings new events for Modal and Refresher, major improvements to dual knob Ranges, and expanded CSS Shadow Parts, laying the groundwork for the next major version of Ionic Framework.
Key highlights:
New Modal drag events provide full drag lifecycle data including position, velocity, progress, and breakpoints
Enhanced dual knob Range support with stable knob identities, new host classes, and new Shadow Parts for styling by identity or position
New Refresher pull events to detect when a pull has started and ended
Expanded CSS Shadow Parts across components for deeper customization
Added support for Angular overlay injectors for Modals and Popovers
Looking ahead:
Modular Ionic: Ionic Framework 9 will make the framework more modular, extendable, and themeable so developers can create and share custom themes inspired by design systems like Liquid Glass
React Router support: Ionic React will support React Router 6 in Ionic Framework 9 first, with future support for React Router 7
Ionic Framework 8.8 enhances customization today while paving the way for the modular architecture and React Router 6 support coming in Ionic Framework 9.
r/ionic • u/Logan-Ionic • Feb 18 '25
Hey all!
As promised, here's an update on what we're working on!: https://ionic.io/blog/coming-soon-new-updates-features-for-ionics-open-source-projects
r/ionic • u/WalkingRiverSoftware • Aug 05 '20
r/ionic • u/iamtherealnapoleon • Feb 11 '25
Today we’re announcing that we have discontinued new customer sales for all Ionic commercial products and services—including Ionic Appflow, Identity Vault, Portals, and all other paid components of the ecosystem.
If you’re using Ionic commercial products:
Appflow users: You’ll continue to have access through December 31, 2027.
Enterprise customers: Ionic understands the disruption that may be caused by discontinuing sales, maintenance, and support of its commercial offerings. In order to support our Enterprise customers through this transition, we will offer an option for continued use and self-service maintenance and support of our commercially licensed software, such as Identity Vault, Auth Connect, Secure Storage, Ionic Portals, and Enterprise AppFlow. We will be in touch directly with existing customers about eligibility, next steps, and continuity plans for each offering.
r/ionic • u/[deleted] • Jun 15 '19
r/ionic • u/Wooden_Food_7685 • Oct 30 '25
I can't claim to have things figured out, but I thought I would post what I think I know so far for anyone else in the same predicament. I am happy to add corrections as needed.
I am new to mobile app dev, and have been fighting insets and status bars for a week - trying to get edge-to-edge to work without major bugs across a variety of Android versions and devices. Since SDK 35+ enforces edge-to-edge, and I think it looks better anyway, I really wanted my app's header background hero image to flow under the status bar, status bar icons to be dark (since my app's only theme is light), and all content displayed with safe area padding.
Bottom line is that it doesn't seem Ionic (nor Capacitor) is prepared for edge-to-edge currently, there are a TON of “just use this plugin” answers floating around the web, and none of them are really solutions on their own.
Context: I am rewriting a legacy app using a modern stack.
Ionic/Vue: 8.7.6
Capacitor: 7.4.3
Node: 24.10.0
JDK: 21.0.8
Target SDK: 36
minSDK: 29
Dev Env: Windows 11, VSCode, using Android Studio to test on various virtual devices and Android versions.
Some apps go for fullscreen - meaning status and navigation bars are completely hidden. When the user swipes up from the bottom or down from the top, they reappear, covering your app. Not what I wanted, so I didn’t mess with it.
My desire is edge-to-edge. Think Google Maps – the map goes all the way to the top of the screen, status bar icons appear on top of the map, but the search bar and all other UI content is safely below the status bar.
Neither of these should be confused with the fullscreen property that can be set on <ion-content>, which only affects how <ion-content> may or may not be permitted to flow under a translucent <ion-header> or <ion-footer>. This setting will NOT affect the behavior of Android status/nav bars, nor WebView margins (the box within which Ionic draws your app).
Some solutions to this challenge focus on limiting the app’s WebView to staying inside the status and navigation bars, and potentially other screen cutouts. If you don’t want an edge-to-edge look, these solutions seem simple and reliable. For those who want an edge-to-edge app, we need the WebView to cover the entire screen – with translucent status and nav bars overlaying the app. IE zero WebView margin.
Other solutions focus on defining safe area padding within the WebView. If you already have a WebView margin set (non-edge-to-edge app), then you probably don’t want to apply safe area padding. The exception may be if one of the plugins is WebView margin aware, and can calculate any additional padding needed for cutouts that aren’t already accounted for in the WebView margin.
Capacitor has added the following option to its configs. (/capacitor.config.ts)
import type { CapacitorConfig } from '@capacitor/cli';
const config: CapacitorConfig = {
...
android: {
adjustMarginsForEdgeToEdge: 'auto' | 'force' | 'disable',
},
...
};
export default config;My use case requires disable (which is the default for cap. v7). In force mode, all versions of Android get a WebView window that starts after the status bar (and I suppose any cutouts?) and ends before the navigation bar. You can theme/color the status and nav bars, but your header hero image or other content cannot cross those boundaries. Mode auto leaves legacy Android versions alone and only applies these margins to the WebView window for devices that have edge-to-edge enabled – basically overriding edge-to-edge enforcement. I can’t see when the result of auto would be any different from force (shrug).
This plugin is a complete misnomer. It does nothing to support edge-to-edge, it overrides edge-to-edge. Now that the adjustMarginsForEdgeToEdge=auto|force option in capacitor.config.ts exists, it is largely unnecessary. It does add a function for enabling/disabling the extra margins. The only reason to use this plugin today is if you want to dynamically resize your WebView from edge-to-edge to within the status/nav bars.
I’ll talk more about this plugin in another section, but it’s worth noting here that it can also affect your WebView margin. The following can conflict with others listed here, and I don’t know who overrides who. These are the settings that complement edge-to-edge:
In capacitor.config.ts:
const config: CapacitorConfig = {
...
plugins: {
StatusBar: {
setOverlaysWebView: true,
};
};
};Or during runtime, call the following after importing the plugin: await StatusBar.setOverlaysWebView({ overlay: true });
This one looked really promising – injecting proper CSS vars for --safe-area-inset-top (etc.) that your app can use to pad content inside a truly edge-to-edge WebView. It overcomes the inconsistent ways safe areas are reported by different devices and versions of Android.
I was even able to alter its example code to directly overwrite the --ion-safe-area-top (etc.) values and leverage default Ionic goodness.
Unfortunately, the current version completely breaks upon rotation. So, I can't use it. https://github.com/AlwaysLoveme/capacitor-plugin-safe-area/issues/43
This one works! Except it’s deprecated prematurely (UGH!). The author wants it rolled into capacitor instead. Until then, just install the version that isn’t empty: npm install @capacitor-community/[email protected]
Follow the old readme (https://www.npmjs.com/package/@capacitor-community/safe-area/v/7.0.0-alpha.1 ).
Then I added the following to my main app.scss to apply the plugin’s accurate safe areas to Ionic’s defaults:
:root {
--ion-safe-area-top: var(--safe-area-inset-top);
--ion-safe-area-bottom: var(--safe-area-inset-bottom);
--ion-safe-area-left: var(--safe-area-inset-left);
--ion-safe-area-right: var(--safe-area-inset-right);
}NOTE: I found that doing this purely from capacitor.config.ts was unreliable on cold starts – it seems to get values too late, and they don’t apply until after a redraw. Setting up the plugin at runtime works best for me – in main.ts, after router is ready, before mounting the app.
Okay, with my WebView successfully edge-to-edge, and with capacitor-community/safe-area giving me accurate safe area padding – I thought I was in pretty good shape!
But now, there are a whole slew of things affecting the color/transparency of the status and nav bar backgrounds, as well as the color of the icons in them.
This seems to be the most commonly recommended. It can be configured in capacitor.config.ts, and/or set at runtime.
const config: CapacitorConfig = {
…
plugins: {
StatusBar: {
…
backgroundColor: '#ffffff00', // Transparent white
style: 'LIGHT', // Use LIGHT for dark colored icons
},
},
…
};Or during runtime: await StatusBar.setBackgroundColor({ color: '#ffffff00' }); await StatusBar.setStyle({ style: Style.Light });
NOTE: color formatted #RRGGBBAA (alpha at the end), and Style.Light means light background and dark icons.
Oh, this gem that’s giving me good safe area padding also tries to set status/nav bar colors / transparency / icon color.
In capacitor.config.ts:
const config: CapacitorConfig = {
...
plugins: {
SafeArea: {
enabled: true,
customColorsForSystemBars: true,
statusBarColor: '#00ffffff',
statusBarContent: 'dark',
navigationBarColor: '#00ffffff',
navigationBarContent: 'dark',
offset: 0,
},
},
};And/or during runtime:
await SafeArea.enable({
config: {
customColorsForSystemBars: true,
statusBarColor: '#00ffffff', // transparent
statusBarContent: 'dark',
navigationBarColor: '#00ffffff', // transparent
navigationBarContent: 'dark',
},
});NOTE: color formatted #AARRGGBB (alpha at the beginning), and content ‘dark’ means dark icons.
Oh, but you may also have competing values linked via AndroidManifest.xml (android:theme="@style/[u]AppTheme[/u]") to \android\app\src\main\res\values\styles.xml
<style name="AppTheme" parent="Theme.AppCompat.Light.DarkActionBar">
...
<item name="android:navigationBarColor">@android:color/transparent</item>
<item name="android:windowLightNavigationBar">true</item>
<item name="android:statusBarColor">@android:color/transparent</item>
<item name="android:windowLightStatusBar">true</item>
</style>These styles are definitely overridden by other capacitor plugins, but there are a couple reasons to set these styles anyway.
When transitioning from splash to my app, I found the settings above would flash in momentarily before capacitor corrected them.
Not all plugin status bar settings survive rotation. Without the above styles set, upon redraw my other plugin settings would fail and I’d get the default white icons on my light-colored hero background again.
NOTE: here windowLightStatusBar true means dark icons.
Here’s what works for me to create an edge-to-edge app with consistent display for all the devices I could test from API 29 through 36:
Set WebView to no margin: (this is default for Capacitor 7, but that will change to ‘auto’ in version 8, so might as well be prepared now.)
In capacitor.config.ts: adjustMarginsForEdgeToEdge='disable'
2. Configure my theme in styles.xml with transparent status and nav bars with dark icons. (be sure you define these colors in the adjacent colors.xml)
<item name="android:navigationBarColor">@color/whiteTransparent</item>
<item name="android:windowLightNavigationBar">true</item>
<item name="android:statusBarColor">@color/whiteTransparent</item>
<item name="android:windowLightStatusBar">true</item>3. capacitor-community/[email protected], called in my apps main.ts after router availability, before mounting the app.
import { SafeArea } from '@capacitor-community/safe-area';
await SafeArea.enable({
config: {
customColorsForSystemBars: true,
statusBarColor: '#00ffffff', // transparent
statusBarContent: 'dark',
navigationBarColor: '#00ffffff', // transparent
navigationBarContent: 'dark',
},
});4. Update main app.scss to update Ionic safe areas with correct ones from the SafeArea plugin:
:root {
--ion-safe-area-top: var(--safe-area-inset-top);
--ion-safe-area-bottom: var(--safe-area-inset-bottom);
--ion-safe-area-left: var(--safe-area-inset-left);
--ion-safe-area-right: var(--safe-area-inset-right);
}5. And then I had to override padding on a bunch of components, because Ionic is not as good at being automatic as they would like to think they are. (For example, I had to remove superfluous --ion-safe-area padding from elements inside an Ion-Popover.)
That’s it – the result of a week of frustration, which equals learning 😊. I hope this helps someone.
r/ionic • u/ThatPigeon • Dec 13 '21
r/ionic • u/mr_hie • Jun 29 '20
Hi Ionic community!
It's me Hieu Pham again. I aim to release 100 free Ionic templates on Github. Here's the 4th one https://github.com/mrhieu/ionic-instagram
Demo: https://mrhieu.github.io/ionic-instagram/
Enjoy prototyping!

iPhone Duo launches today, and Ionic Theme iOS27 v2.0 is finally here! 🎉
I've been working on this for a while, and I'm really excited to finally share the stable release!
The biggest change since the preview is that I've separated the theme and Native UI into two packages.
The capacitor-native-ui plugin now works with any Ionic theme, including your own custom theme. And here's the fun part: it also works with plain HTML, without Ionic Framework!
On supported iOS devices, you can render Ionic controls using UIKit and SwiftUI while keeping your existing WebView, routing, and event handlers.
And yes, iPhone Duo is supported too! 📱
With adaptive layouts and native vertical tab bars, the same Ionic app can work across both form factors. You'll need to install and configure the plugins, but there's no need to build a separate UI just for Duo.
Check out the video to see it in action!
A big thanks to Erkam Yaman for his capacitor-foldable plugin, which provides the device and layout information that makes this possible. 🙌
Everything is open source under MIT:
https://github.com/rdlabo-dev/ionic-theme-ios27
If you're building something with Ionic or Capacitor, I'd love for you to give it a try. And if you find it useful, please share it with other developers!
I'd love to hear what you think! 🚀
r/ionic • u/ivanm5 • Sep 14 '26
The most likely scenario on 23 October. Your Capacitor app on the App Store is built with the iOS 26 SDK or an earlier one: Apple has required the iOS 26 SDK for uploads since 28 April 2026 and has announced no iOS 27 requirement. Apple's talk Prepare your app for iPhone Duo says "Your app runs on iPhone Duo even without recompiling, but screen usage improves with each SDK", and in the talk an app not built with the iOS 27 SDK "will be a familiar size and aspect ratio" on the open device. So the app shows its phone layout in a phone-shaped window, with its tab bar at the bottom, as on any iPhone. The inner display ignores supported orientations (same talk, 2:46), so a portrait lock does not keep an app out of landscape.
What your app gets, by the SDK you build with. Point sizes assume the 3x of current iPhones; Apple has published pixels only.
| Built with | Open (inner display) | Closed (outer display) | Bars | A stock Ionic app |
|---|---|---|---|---|
| iOS 26 SDK or earlier: every build uploaded today | "a familiar size and aspect ratio" | "the screen space to the left of the status bar and camera" | horizontal, where the app draws them | its phone layout |
| iOS 27 SDK: Xcode 27, which needs the UIScene lifecycle (Capacitor 8.5) | "extends your app left of the status bar"; size not published | not stated | horizontal | not predictable until the size is known |
| iOS 27.1 SDK: Xcode 27.1 beta is "coming later this month" | "reaches the screen edge"; regular width and height; about 669 × 951 pt by the App Store screenshot size, 626 × 890 pt by the panel | about 466 × 678 pt | native navigation and toolbar buttons move to the side; an HTML ion-tab-bar stays where the app draws it | md (768 px) rules in landscape only; the split pane (992 px default) never opens |
Area by area, for an iOS 27.1 SDK build. The image marks five areas of one Ionic screen (Calendar, iPhone 16 simulator). Each area below has what Apple says happens on Duo, what the area is in an Ionic app, and what to do. Nothing here ran on iPhone Duo.
1. Status bar and Dynamic Island (system)
On Duo: the HIG lists them with the bars: "Controls on the side include both system and app elements: the Dynamic Island, the status bar, the toolbar (including navigation buttons), and the tab bar." The bars sit on the side on the outer display and on the inner display in landscape, and return "to a familiar horizontal layout in portrait" (talk 111462, 0:28).
In Ionic: the starters set viewport-fit=cover, Capacitor's ios.contentInset defaults to never, and Ionic's core.css sets --ion-safe-area-left and -right from env(safe-area-inset-left) and -right. The side inset reaches your CSS through those variables. Which values the web view reports on Duo is untested.
What to do: handle left and right separately: "Safe areas and layout margins are often asymmetric on iPhone Duo, so handle each side independently and test in Split View" (talk 111461, 6:06). Remove arithmetic on insets: in my build max(10px, safe-area − 12px) put a FAB 49 pt too high when the bottom inset changed from 34 to 83 pt.
2 and 3. Header toolbars (ion-header › ion-toolbar, HTML)
On Duo: native toolbars and navigation buttons move to the side. When space runs out, "toolbars compress first by default" into the system overflow menu (talk 111462, 12:23). Controls "too wide to fit in this vertical space" stay horizontal (talk 111466, 5:07), which covers a week strip like area 3.
In Ionic: ion-toolbar is HTML inside the web view, so it stays a row at the top in every pose and never folds into the system overflow menu. It pads with --ion-safe-area-left and -right; ion-header pads the top with --ion-safe-area-top.
What to do: on the outer display the side region also holds "dynamic elements like live activities and the status bar" (talk 111466, 5:07), so check that end-slot buttons clear the side inset in landscape. Put extra actions in an ion-popover or ion-action-sheet yourself: the web toolbar has no automatic overflow.
4. Content (ion-content, HTML, scrolls)
On Duo: the app is resized on fold, unfold and Split View: "All apps participate in multitasking on iPhone Duo, where two apps sit side by side" (talk 111464, 2:59). Apple's rule for the fold: "Continuously scrolling content like articles and feeds shouldn't displace" (talk 111463, 2:26). "The system automatically repositions action sheets, alerts, menus, and popovers around reserved regions to keep them fully visible" (5:12).
In Ionic: ion-item, ion-item-divider, ion-list-header, ion-card and ion-fab pad with the side insets; ion-content itself has no safe-area rule. ion-alert, ion-action-sheet and ion-popover are drawn inside the web view, so the system's repositioning does not reach them. Capacitor's Dialog and Action Sheet plugins present native dialogs and action sheets. No web API reports the fold: the iOS 27.0 SDK's WebKit headers have no fold or segment symbol, and WebKit's Viewport Segments position has been open since March 2024.
What to do: choose the layout from the size class instead of the width, by sending horizontalSizeClass from native code to the web view as a class on the root element. The inner display is regular in both dimensions (talk 111461, 2:46) but 626–669 pt wide in portrait at 3x, below Ionic's lg (992 px), so an ion-split-pane with the default when, as in Ionic's sidemenu starters, never opens. Keep the route, selections and drafts in the URL or a store: in my build each crossing of a 672 px breakpoint remounted the router outlet. For prompts that must stay clear of the fold, try the native Dialog and Action Sheet plugins; their behaviour on Duo is untested.
5. Tab bar (ion-tab-bar, HTML)
On Duo: tab bars move to the side. Apple says to "use bars provided by navigation containers" (talk 111462, 2:00) and lists TabView and UITabBarController as "fully adaptive across every pose" (talk 111461, 5:01).
In Ionic: ion-tab-bar stays at the bottom in every pose and pads left, right and bottom with the insets. None of Capacitor's 38 official plugins is a tab bar.
What to do: for the side placement, the tab bar has to be UIKit. With @capgo/capacitor-native-navigation 8.3.1, my build's bar became a UITabBarController in 154 lines of TS, CSS and JSON with no Swift, and in an 816 pt iPad window it turned into the floating top bar with no JavaScript written for that. I have not run it with the iOS 27.1 SDK. Keeping ion-tab-bar means a bottom bar in every pose.
What to expect from Ionic and Capacitor
Capacitor 8.5 (31 July) adopts UIScene: "until you adopt scenes, Xcode 27 is closed to you", and "Published apps keep running on iOS 27, and so will anything you build with Xcode 26."
Capacitor 9 is "forecasted to launch at the end of November" with "a compatibility floor" for foldable and large-screen devices. iPhone Duo ships 23 October.
No GitHub issue about iPhone Duo exists in ionic-team/capacitor, ionic-framework or capacitor-plugins (searched 14 September). The only search hit is a thread of 11 September comments in ionic-framework #30466, where the commenter was asked to open one.
Apple's 23 September Q&A sessions cover Photos & Camera, SwiftUI and UIKit; none names web content.
Order of work
For 23 October, ship your iOS 26 SDK build as it is.
Adopt Capacitor 8.5 and its UIScene migration, so Xcode 27 builds work. Keep one scene until your plugins are tested with two bridges.
Before an iOS 27.1 SDK build: layout by size class, state in the URL or a store, insets per side without arithmetic, and a decision on the tab bar.
When Xcode 27.1 beta ships, run the Duo simulator in each pose and in Split View, and read innerWidth, the four env(safe-area-inset-*) values and where each bar is drawn.
Nothing here ran on iPhone Duo or its SDK. I will post the Duo simulator results when Xcode 27.1 beta lands.
Sources (read 14 September 2026): Apple tech talks 111461, 111462, 111463, 111464, 111466; HIG; App Store Connect screenshot sizes; iPhone Duo tech specs; Apple's upcoming requirements; Capacitor 8.5; The Road to Capacitor 9; Capacitor configuration; Capacitor plugins; ion-split-pane; WebKit standards-positions #327; capacitor-native-navigation; the 0:29 quotes as transcribed in Blake Crosley's write-up.
--
Disclosure: I'm building Modaal, an AI app builder that outputs native Swift and Kotlin projects, so I have a stake in native apps. Every claim above links to its source, and the full project built for the measurements is available on request.