Hi everyone.
If your app uses embedded app methods, then it must do so consistently. This means that it must provide a consistent embedded user interface experience that begins after authentication.
Here’s our case.
- We have a SaaS product Pics.io that can, among other great things, store merchant’s product photos
- Our customers (who also run Shopify stores) requested that we make an import app to bulk transfer those photos from their libraries to their Shopify stores, to reduce manual work X times
- We made such an app as an embedded app. It’s very basic: a user log ins with his creds, we access their library of photos, match all photos by a field that contains SKU with SKUs of products in Shopify, and, if there are matches, upload those photos to matched products in Shopify. Here’s a screencast of how it works https://show.pics.io/preview/61ae0390c78e770012bf5683
In short, we are told that an embedded app cannot do imports, it should allow to upload images directly to Shopify’s UI. That way the app would be in line with the requirement above. But for our users this would make 0 sense: that already have images stored in libraries in our SaaS, they don’t want a separate app to upload the same images into Shopify, creating duplicates (originals are stored in
Pics.io, duplicates in Shopify).