Drawbacks to creating an Affirm / Klarna comp in Retool Embed?

Discussion
1

Hey guys,

I'm wondering if Retool Embed would be good for my use case, and what potential drawbacks there may be. To clarify, here are my requirements:

  • When a user clicks on a button on an ecommerce website, it'll launch my Retool Embed application via an iFrame
  • The ecommerce website should pass data to the iFrame to call my backend API's
  • The Retool Embed application should have access to my backend API's, which are secured with oauth RBAC
  • The Retool embed application has multiple "stages", but each unique user click will route it to the initial "stage"
  • If a user has already gone through the Retool Embed workflow, clicking the link again should not take them to the initial "stage"

The requirements are fairly similar to buy-now-pay-later providers like Klarna, Affirm, Credit Key, etc. Any insight would be appreciated!

2

Hello @Adrian_Tran!

Great questions, wish I had more details on anything specific to watch out for. The only hiccups might be on passing data into and out of the iFrame window.

I would highly recommend going through our docs here and also here.

We recently launched the Embedded JS SDK so we are looking to get as much feedback on that as possible.

For your 4th bullet point, stages might be tricky to implement. We have a few components such as Breadcrumbs and Wizard but there are some limitations. Definitely check out their docs here and here to learn more about them.

We are looking to roll out multi paged apps shortly which should replace a lot of these multi-step use cases.

For your las bullet point, being able to track the users progression in the front end state to ensure it doesn't start them from the beginning should be possible but will need some solid architecture depending on if you try to store this information in the frontend state or if you are able to log users current progress into the backend/DB to keep things on track.