feat: platform-agnostic base style
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- typescript
Rechercherichtung
Beginne damit, die vorhandenen plattformspezifischen iOS- und Material-Stile für die Content-, Modal-, Router- und Navigationskomponenten zu überprüfen. Vergleiche ihr gemeinsames Verhalten und ihre Anpassungspunkte und lege anschließend den Umfang eines plattformunabhängigen Basisthemes fest. Als abgeschlossen gilt die Aufgabe, wenn ein abgestimmtes Design und ein Implementierungsplan für sinnvolle Standardwerte, Anpassungen, Übergänge und Gesten vorliegen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Prerequisites
- I have read the Contributing Guidelines.
- I agree to follow the Code of Conduct.
- I have searched for existing issues that already include this feature request, without success.
Describe the Feature Request
tl;dr: Introduce a new minimal "base" style, which is platform-agnostic and more customizable than the current platform-specific styles.
I've been using Ionic for 8 years now in a production app with great success. When liquid glass was announced, my first thought was that this could become a problem for Ionic and other cross-platform frameworks, because they usually have one style per platform, but not per OS version number. If Ionic adjusts to liquid glass, it will be the same style even for devices running anything < iOS 26. Now, Ionic has the problem that it looks like "old iOS" on iOS 26 devices.
However, after using the mess which is called liquid glass, I'm convinced that app developers won't even bother with making their app look Apple-like and rebuilding liquid glass in CSS is a waste of time. Liquid glass is so opinionated that devs might actually go for a more unified style for both Android and iOS just like Flutter apps, which have pixel-perfect matching styles. For React Native, it's similar. While they do have platform-specific styles, big apps try to use their own design system instead of going for that Apple- or Material-specific look. UI libraries like shadcn/ui are on the rise, which give apps a unified look.
Flutter seems to be surprisingly popular, too, even though they don't even give you simple OS-level tools like text selection, copy-paste etc. which you get for free in an Ionic app.
Ionic is still unique, because it gives devs sensible defaults, a great dev experience, good basics like page transitions, modal transitions, gestures, toggles, a router and I love the idea that Ionic components are just Web components. Another framework that tries to mimic liquid glass is KonstaUI, but they lack transitions and gestures. I also thought about creating my own mini-framework that is mostly without styles, but this made me appreciate all of the tiny things that Ionic does right even more (especially transitions, gestures, the whole overscroll/rubberbanding effect etc.)
On modern devices, I don't really see the reason to use Flutter, because why would I need a custom rendering engine if Chrome and Safari can be my rendering engines and I can write HTML/CSS/JS to make true cross-platform apps with a single code base.
The biggest disadvantage of Ionic is that it is hard to customize the theme, partially because the web components use ShadowDOM, partially because "ios" and "md" are deeply entrenched in the framework. What I'd like to see and maybe this is a vision that'd work for the Ionic team, too:
Make a new "base" theme that can easily be customized. Maybe the base theme could have mostly unstyled components or comes only with the bare minimum components to make a SPA feel applike: content, header, modal, router, transitions including all gestures etc.
Anyways, I just wanted to put this out here and hear from people what they think about this.
Describe the Use Case
Apps that want to have more of their own design system without using Material or Liquid Glass.
Describe Preferred Solution
Make content, modal, router, nav have a sensible base style that works on both platforms, make them open so that I could customize transition speeds etc. but still get a great UI out of the box.
Describe Alternatives
Build my own, but then lose access to all the work that went into optimizing the "headless" part of Ionic core components.
Related Code
No response
Additional Information
No response
- Vorherrschende Sprache
- TypeScript
- Sterne
- 52.8k
- Forks
- 13.3k
- Ø Merge
- 3 T. 1 Std.
- Gemergte PRs (30 T.)
- 86
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus ionic-team/ionic-framework
-
bug: input-otp, backspace in an empty box only moves focus instead of clearing the previous boxEvtl. vergeben @sarankumar1325 hat das vor 23 Tagen übernommen. Offenpackage: core type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
ionic-team/ionic-framework#31639 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug: vue swipe cancellation throws when the previous page is missingEvtl. vergeben @dandoingdev hat das vor 46 Tagen übernommen. Offenpackage: vue type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
ionic-team/ionic-framework#31514 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug: ion-searchbar input is always labelled "search text"; aria-label on the host is not forwardedEvtl. vergeben @HappyKnuckles hat das vor 41 Tagen übernommen. Offena11y package: core type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
ionic-team/ionic-framework#31492 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug: IonTabs throws when a Fragment contains one IonRouterOutletEvtl. vergeben @Benziza hat das vor 82 Tagen übernommen. Offenpackage: react type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
ionic-team/ionic-framework#31410 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug: angular swipe-back gesture crashes in StackController.startBackTransition when the stack is popped before the gesture is capturedEvtl. vergeben @officialasishkumar hat das vor 9 Tagen übernommen. Offenpackage: angular type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
ionic-team/ionic-framework#31291 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in ionic-team/ionic-framework
Ähnliche Issues
-
area-templates triage:bot-seen triage:needs-human
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
microsoft/aspire#22356 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Archiving an agent that is not loaded keeps its old updatedAtEvtl. vergeben @luoph hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
content triage
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
-
contributor: external needs review severity: low
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
expo/expo#53642 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
JSPrismarine/JSPrismarine#3214 ·
Maintainer antworten meist innerhalb von 1 Tag