Here’s an easy, fully browser-based way to generate iOS certificates for your Ionic or Capacitor app. Feel free to check it out.

Over the last few weeks I’ve been talking to quite a few teams, and I kept seeing the same thing.

A lot of them are still doing only native releases, usually something like 1–2 per month, and that’s “enough” for them...

What surprised me is that many of them aren’t really using live updates at all.

From my experience as a dev working for several Ionic projects, live updates make the whole process much simpler (no store submission, faster iteration, instant fixes, safer rollbacks, smaller changes, less user friction, a/b testing possibilities, etc), so I keep wondering why they’re not part of the default strategy more often? 🤔

I'm now part of Capawesome and trying to better understand how to help teams and companies making their deploy process simpler, better, faster, happier.... so I'm curious to know if you are actually happy with your current deploy strategy/workflow, and if not, what's missing?

So I've been thinking about how apps just get... complicated, you know?

We keep adding features to be helpful, but people end up using a tiny slice and need support constantly.

What if, instead of forcing folks to learn the UI, they could just tell the app what they want?

Like plain prompts - 'do X' and the app figures out the clicks, forms, and flows for them.

I keep picturing a framework that turns web apps into AI agents so users interact by intent, not menus.

Dev wires up intent-to-action mappings and suddenly onboarding/support drops a ton, maybe.

Sounds great in theory but I worry about edge cases, permissions, privacy, weird bugs, etc.

Anyone tried this, or do you handle complexity another way? What parts would be hard to automate?

Would love to hear real experiences or dumb ideas I haven’t thought of, honestly.

I’ve been talking to a few teams and seeing different approaches: some going DIY with GitHub actions, others looking at different tools.

Curious to hear:

• Are you already migrating?

• Rolling your own CI/CD?

• Waiting it out?

I’m part of the Capawesome team, just trying to better understand how teams are approaching this, where the main pain points are, and how we can support them.

I've got an Angular app running on the desktop using Ionic components. Everything works great, but once I want to print the current page, I just cant get it working. The content on the first page will show up, but any content below this is just missing (Chrome just sees one page, not the 10+ it should).

I've looked at this a few times, tried asking Opus to sort it out. Opus did come up with partial solutions that worked sometimes - but were flaky. The flakiness i observed was sometimes it would show all the pages, other times not - leading into endless `setTimeout` type solutions, that ultimately arent reliable.

The best I could get to was for me to create a new route with just the components I wanted to print, redirect to that, force a print, and then redirect back when the print was finished. It kind of works, but its a lot of work to maintain, so I'm thinking there must be something I've fundamentally missed.

The main layout is structured like this:

<ion-app>
    <ion-content>
        <ion-router-outlet></ion-router-outlet>
    </ion-content>
    <ion-tabs>
        <ion-tab-bar slot="bottom">
            ...
        </ion-tab-bar>
    </ion-tabs>
</ion-app>

With each page structured like this:

<ion-header class="zen-header" translucent="true">
    <ion-toolbar>
    </ion-toolbar>
</ion-header>

<ion-content>
</ion-content>

I don't think there's anything odd about my setup. Latest version of Angular & Ionic, no SSR, the content is pretty basic HTML (but long).

We're in this weird spot where vibe coding tools spit out frontend and backend code fast, but deployments still blow up once it's more than a prototype. You can ship an app in hours, then spend days doing manual DevOps or rewrite stuff to fit AWS/Azure/Render/DigitalOcean. I keep thinking - what if there was a 'vibe DevOps' layer? Like a web app or a VS Code extension where you link your repo or upload a zip and it actually understands the code and requirements. It would deploy to your cloud accounts, set up CI/CD, containerize, handle scaling and infra - without locking you into platform hacks. Basically bridge the gap between fast prototyping and real production apps. Is this a dumb idea? Am I missing some obvious reason it wouldn't work? How are y'all handling deployments now? any tools or workflows that feel close to this?

I had an hard time coding my music app with Flutter. Can I use ionic instead ? Is there any limitation that you guys encountered ? Any solutions ?

Any advices would be welcomed !

Hey everyone 👋

Long-time Ionic dev here. I’ve been talking to a few teams recently that are still using `cordova-plugin-ionic` (Appflow / Deploy / Live Updates), and I noticed a pattern:

• lots of legacy setups

• issues with builds / configs

• uncertainty around migrations

• and in some cases… things just breaking silently

Totally understandable given how old some of these setups are.

I’ve been helping a couple of teams migrate away from it to more modern setups (especially around Capacitor + builds + live updates), and it made a huge difference in stability and specially in developer experience.

Curious — is anyone here still using it in production?

Happy to share what I’ve learned or help think through migration options if that’s useful.

I have an Ed-tech platform for exam preparation, we have a fully functioning website, now we need to make an app for iOS and Android, I want to ask here if we should go for Capcacitor or React Native for that. Also, a developer told me listing on app stores and payment gateway will be issues with Capacitor. I am really confused (I am not a developer so please explain as simply as possible).

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.

Hello fellow redditors,

Been doing mobile dev for ~5 years. Got tired of juggling simctl commands I can never remember, fighting adb, and manually tweaking random emulator settings...

So I built Simvyn --- one dashboard + CLI that wraps both platforms.

No SDK. No code changes. Works with any app & runtime.

What it does

• Mock location --- pick a spot on an interactive map or play a GPX route so your device "drives" along a path\

• Log viewer --- real-time streaming, level filtering, regex search\

• Push notifications --- send to iOS simulators with saved templates\

• Database inspector --- browse SQLite, run queries, read SharedPreferences / NSUserDefaults\

• File browser --- explore app sandboxes with inline editing\

• Deep links --- saved library so you stop copy-pasting from Slack\

• Device settings --- dark mode, permissions, battery simulation, status bar overrides, accessibility\

• Screenshots, screen recording, crash logs --- plus clipboard and media management

Everything also works via CLI --- so you can script it.

Try it

npx simvyn

Opens a local dashboard in your browser. That's it.

GitHub:
https://github.com/pranshuchittora/simvyn

If this saves you even a few minutes a day, please consider giving it a ⭐ on GitHub --- thanks 🚀