Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- App Bridge adds safe area padding to the bottom of the main app document. This does not mean every custom surface is automatically adapted.
- Fixed or sticky controls, custom scroll containers, and s-app-window content must apply safe area insets themselves. Legacy modals without the App Bridge CDN script may also be covered.
- The announcement recommends App Bridge toasts, which appear at the top of the frame, away from Sidekick.
- It also recommends Sidekick App Extensions. A developer’s question about integrating without Shopify Managed Install has no staff answer in the current discussion.
Identify the change at the bottom of the admin
The announcement connects the new placement to the recent Shopify admin visual update: Sidekick appears at the bottom center of every admin screen, including embedded apps. The staff member explicitly says there is no API to hide or disable it.
Focus on whether app content remains visible and usable rather than planning around an unavailable hide switch. The announcement does not introduce a fee, country or plan condition, or a remediation deadline.
Automatic document padding does not cover every custom surface
According to the announcement, the App Bridge library adds safe area padding to the bottom of the main app document to prevent Sidekick and other admin controls from covering important content. This describes the main document; it is not a blanket guarantee for every custom layout.
The staff member separately identifies fixed or sticky controls, custom scroll containers, and content inside s-app-window: these must apply safe area insets themselves. Space at the bottom of the main page does not establish that those surfaces have received the same treatment.
Check fixed action bars, scroll containers, and legacy modals
Consider a hypothetical order editor: the page body scrolls normally, but a Save action bar stays fixed at the bottom. Padding on the main document does not establish that the fixed bar clears Sidekick. It remains one of the controls that the announcement says must handle safe area insets itself. This example explains layout responsibility; it is not a reproduction of a particular app failure.
Review custom scroll containers and s-app-window content in the same way. The announcement also warns that Sidekick may cover content near the bottom of legacy modals that do not load the App Bridge CDN script. Do not assume that the main page’s behavior carries over to these separate surfaces.
Keep notifications visible with App Bridge toasts
For embedded apps, the announcement recommends App Bridge toasts. These appear at the top of the frame, where the staff member says Sidekick will not block them.
If your app places custom notifications at the bottom, treat this recommendation separately from fixed-control layout work. One concerns how a notification is presented; the other concerns the safe area a layout must respect. Do not assume that document padding automatically repositions a custom notification.
Separate the integration recommendation from unanswered eligibility questions
For all apps, the announcement says to use Sidekick as the app’s AI chat entry point and integrate Sidekick App Extensions to provide read and write tools connected to the app. That is the direction stated in the post. It does not establish that every app already meets the same integration conditions or must finish by a particular date.
Developers in the discussion raise questions about their own AI products, usage restrictions, and integrating without Shopify Managed Install. The complete current three-post discussion contains no staff follow-up answering them. A user’s reported delisting experience is also insufficient to establish a new review or delisting rule.
Plan changes by surface and keep unanswered limits explicit
Review the main document, fixed or sticky action bars, custom scrolling areas, s-app-window, legacy modals, and notifications separately. Identify whether each relies on automatic padding, needs its own inset handling, or should use App Bridge toasts. For specific safe area syntax, follow the Environment API reference linked from the announcement.
The announcement provides no exact CSS property or code example and no complete plan, country, pricing, or Managed Install eligibility matrix. Do not use it to tell every merchant to change plans, reinstall an app, or use an undocumented hiding workaround.
Sources
Frequently Asked Questions
Can one fixed amount of bottom padding handle every layout?
The announcement gives no universal pixel value. Main documents, fixed controls, and custom scrolling areas have different responsibilities, so a guessed height cannot guarantee every layout works. Follow the linked Environment API reference for the specific safe area syntax.
Must an app immediately shut down its own AI chat feature?
The post directs apps to use Sidekick as the AI chat entry point and recommends Sidekick App Extensions, but gives no universal shutdown instruction, enforcement date, or delisting rule for existing AI features. Questions about proprietary AI and usage restrictions have no staff answer in the discussion; additional mandatory measures cannot be inferred.
Does a visible save notification prove the order was saved?
Top placement addresses whether the notification is covered. Confirm a save through the app’s processing result and the corresponding order state. Notification placement alone does not establish that a business operation succeeded.