-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect TWA or PWA request #192
Comments
At first glance I don't think we can. As this package only works with the HTTP requests made toward the server and processes the User-Agent header, any client side behaviour should be detected on the client. TWA should make no difference in the application's backend code. |
Sometimes application markets can remove the application from the market because there are payment screens on the sites. There may be a need to convert the website to PWA and publish them in application markets (TWA). In order to prevent the application from being removed from the markets, phrases such as "Please continue on the website" are written where the payment sections are. Wouldn't that be useful for controlling it ? |
Oh I think there is a misunderstanding. This package only works from the HTTP request's User Agent header. Your use case seems to be a 100% client side. ^.^ |
Can we detect requests opened via TWA (Trusted Web Application) through this package?
The text was updated successfully, but these errors were encountered: