Replies: 2 comments
-
|
I'm right there with you and I agree with your thinking. My only (!) concern is that people might "abuse" it to build a Tauri-like version of perry - which is not the idea. That being said, I don't know if the concern here outweights the benefits. Because you are right, native apps still need to display webcontent. Thinking this through ... |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@nandy007 Here you go: https://docs.perryts.com/ui/webview.html (avallable on newest main) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Even in a native-first architecture, Web content is still a first-class requirement in production apps.such as:
OAuth / authentication flows (Google, GitHub, etc.)
Payment providers (Stripe, PayPal, etc.)
Embedded admin dashboards or CMS systems
Legacy web modules that are not yet migrated to native UI
Rich content rendering (Markdown, HTML-based editors)
External partner integrations
So I would like to raise a feature request regarding WebView integration across platforms.
Beta Was this translation helpful? Give feedback.
All reactions