Skip to content

Use Case: 3rd Party Content for Secure Sites #114

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

Open
ChadKillingsworth opened this issue May 9, 2019 · 5 comments
Open

Use Case: 3rd Party Content for Secure Sites #114

ChadKillingsworth opened this issue May 9, 2019 · 5 comments
Labels
explainer input Issues which contain information to be incorporated into the explainer or use cases document

Comments

@ChadKillingsworth
Copy link

I just wanted to document my use case and re-enforce the utility that portals would bring.

I develop an online banking platform for hundreds of US based financial institutions. We're planning on allowing 3rd parties to provide rich web apps embedded in our site via sandboxed iframes. However navigation will take the user to the 3rd party site. After seeing portals, it seems like a much better experience and highly preferable to a standard iframe.

Since this is outside of the standard link aggregation site use case, I wanted to re-enforce the utility in other types of sites.

@lucasgadani
Copy link
Collaborator

Thanks for the feedback! Yes, this is one of the main use cases we have considered since the start of the design. Basically, we want to be able to provide a user experience where the user transitions from a page, to a payment processor, back to the page, with smooth transitions, but at the same time being able to verify the origin of the payment processor through the URL bar, which isn't possible with iframes.

@sucrose
Copy link

sucrose commented May 10, 2019

@ChadKillingsworth Your use case is to use portals to transition users away from your platform?

@ChadKillingsworth
Copy link
Author

Yes. Imagine a portal embedded in your online banking site that shows investment accounts at a brokerage. Or invoices and payments from a small business budget site. Interaction with these sites would indeed take you away from my platform.

This allows a financial institution to partner with another provider and provide rich interactive launch points within my platform.

@ChadKillingsworth
Copy link
Author

History / Back button support would be important for us. The version of portals in Chrome Canary doesn't seem to work with the back button. I'm not sure that's intentional though.

@lucasgadani
Copy link
Collaborator

@ChadKillingsworth This is a known issue and it's tracked on #19 .

@domenic domenic added the explainer input Issues which contain information to be incorporated into the explainer or use cases document label May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
explainer input Issues which contain information to be incorporated into the explainer or use cases document
Projects
None yet
Development

No branches or pull requests

4 participants