You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get asked about iOS support fairly often, so here is where I stand and what I think is realistic. Tell me if you see it differently.
The short version
m3e is a Material 3 Expressive editor. The parts, the theme controls, the motion settings and the prompt all follow Material 3. I do not plan to add iOS components to the editor itself.
Why not both
Every part in the editor has one look, one set of controls and one description in the prompt, in four languages. Adding an iOS rendering of each part would roughly double what has to be built and kept in sync, and the two design systems disagree on basics: navigation bars vs. tab bars, FABs vs. toolbar actions, sheet behaviour, corner shapes, typography. A half-finished iOS mode would be worse than none.
What could be done instead
A platform hint in the prompt. The prompt already names a target (Android or web). An "iOS" target could tell the implementing tool to keep the structure and content of the screens but translate the parts to their native equivalents (SwiftUI, Human Interface Guidelines). The canvas stays Material; the output does not have to.
Nothing in the editor, a separate project for iOS. The canvas, frames, tap-to-open flow and prompt generator are reusable; a sibling project with an iOS parts library could share them. That is a lot of work and I am not going to start it, but I would point people to it if someone did.
What I would like to hear
If you asked for iOS: what do you actually need? A prompt that produces a SwiftUI app from a Material sketch, or a canvas that looks like iOS while you design?
Would a platform hint in the prompt cover your case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I get asked about iOS support fairly often, so here is where I stand and what I think is realistic. Tell me if you see it differently.
The short version
m3e is a Material 3 Expressive editor. The parts, the theme controls, the motion settings and the prompt all follow Material 3. I do not plan to add iOS components to the editor itself.
Why not both
Every part in the editor has one look, one set of controls and one description in the prompt, in four languages. Adding an iOS rendering of each part would roughly double what has to be built and kept in sync, and the two design systems disagree on basics: navigation bars vs. tab bars, FABs vs. toolbar actions, sheet behaviour, corner shapes, typography. A half-finished iOS mode would be worse than none.
What could be done instead
What I would like to hear
All reactions