Hey all,
We’re a SasS company trying to launch Shopify Integration (as a Public app) for our Product - Promotion Engine called Voucherify. We’ve recently ran into issues with our app review regarding app embedding.
Currently, when using our Shopify Integration through Shopify Admin context, users can:
- to register to Voucherify
- login to Voucherify
- Connect Voucherify project to their Shopify Store
- Sync data between Shopify Store and Voucherify.
And when using Voucherify directly users are able to:
- send discount coupons from Voucherify to Shopify Store (which will be visible in Shopify Store Discounts tab)
- Subscribe to our platform (this also triggers Shopify Billing API subscription)
- do other things not fully related to Shopify Integration
So in the end, there are two places (two different screens / two different contexts) that our users can use to interact with this Shopify Integration.
- Users can use our Voucherify Dashboard to send discount codes
- Users can log in to Shopify Admin to Shopify Integration and sync data.
So to use our Shopify Integration fully, you need to switch contexts: from Shopify Store (embedded in the Shopify Admin), to Voucherify (standalone application).
This creates issue during review process:
(…) I would like to point out that it is best to make the app fully embedded or fully non-embedded for the best merchant experience. With it’s current set up, the app embedded UI where the user can do the synchronization, while the main function of the app needed to be done to a non-embedded UI. You can make the portal embedded within the app OR make the whole thing non-embedded. See this screencast for additional details.> > (…) Now, if your app should work within the Shopify Admin, it should only be inside the admin and no other features or function that will go outside of Shopify. For example, if the app will need to go to the app dashboard, it should not go to the other tab and load the dashboard separately, it should load within the Shopify admin itself. However, if you intend to have the app load in another tab and not within the Shopify Admin, all of the function should be non-embedded. Meaning, once the merchant access your app on the App index, it should redirect to your app UI right away in a separate tab.> > (…) All the Shopify-related features should be in the embedded or non-embedded version, whichever you decided in doing so.
As far as we understand, the reviewer would like to put all of our Voucherify features directly into the Shopify Plugin - which is not possible to say at least. But we’re wondering if maybe we could just take all the settings from our plugin (leaving just the register, login and project connection process - see screens below) and put it directly in Voucherify. Then you would only be able to sync data between Shopify Store and Voucherify through Voucherify (and not through Shopify Integration).
Could this mean that the Integration would be fully non-embedded and I should uncheck this option shown below?
And more importantly: This would render the Shopify Integration as a blank page (because we only ask for login and project connection during install) - could we just put there some standard page saying that the Shopify Integration connection is successful and log in to the Voucherify to set up the synchronization”? Or would it still make this as a hybrid embedded and non-embedded app?
What is the correct way to tackle this kind of Shopify Integration, where you do not want to put everything into the Shopify Admin embedded view, but rather to split it between Shopify Admin and your standalone application? Or maybe we can only make the barebone Shopify Integration (with just the register, login and connect process) and move the rest of Shopify Integration settings to our standalone app?