What Shopify's Built for Shopify Badge Actually Certifies — and Its Limits

·1 views

The Built for Shopify badge is Shopify's highest recognition tier for App Store apps, certifying that an app has passed the platform's own testing for performance, design, and integration. For storefront-rendering apps, the badge confirms the app reduced a store's Lighthouse score by no more than 10 points in Shopify's internal testing. To qualify, an app must have at least 50 net installs from active paid-plan stores and five reviews, meaning newer apps are excluded regardless of quality. Badged apps rank higher in App Store search results, so top search positions partly reflect badge status rather than pure relevance or fit. The badge does not cover pricing, customer support quality, or suitability for a specific store, and merchants are advised to verify those factors independently.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Route Shopify Webhooks into Google Sheets: Tools and Workarounds

Shopify webhooks cannot send event data directly to a Google Sheets URL, as the spreadsheet has no built-in mechanism to receive and respond to incoming HTTP requests. A middleware layer is required, such as Zapier, Make, or n8n, each of which can receive the webhook and then write a row to a sheet. Alternatively, a Google Apps Script web app can serve as the receiver via its doPost function, though developers must ensure it returns a proper 200 status code to avoid Shopify automatically deleting the webhook subscription. Shopify merchants on Basic, Grow, Advanced, or Plus plans can also bypass webhooks entirely by using Shopify Flow's native 'Add row to spreadsheet' action. Self-hosted n8n users should note that Shopify does not allow webhooks to be sent to localhost addresses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Memory Bandwidth, Not VRAM Size, Determines Local LLM Token Speed

When running large language models locally, memory bandwidth in gigabytes per second is the primary factor governing token generation speed, not the total amount of VRAM available. Because autoregressive decoding requires the GPU to stream every model weight from VRAM for each token generated, the theoretical speed ceiling equals memory bandwidth divided by model size. Benchmarks illustrate the stakes sharply: an RTX 4060 Ti running Llama 8B at 42.5 tokens per second dropped to just 3.8 tokens per second when only 20 percent of weights spilled into system RAM, a 91 percent slowdown. Bus width drives this gap — the same 16 GB of VRAM delivers 288 GB/s on a 128-bit RTX 4060 Ti versus 672 GB/s on the 256-bit RTX 4070 Ti Super. For users seeking the best value, a used RTX 3090 with 24 GB on a 384-bit bus at around $650–750 remains the recommended choice for running 32-billion-parameter models with room for context.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenAI Launches Always-On Agents as Nvidia Debuts Runtime Safety Watchdog

OpenAI introduced Dots at DevDay, autonomous agents that run continuously on cloud infrastructure, connect to over 4,000 apps, and proactively seek tasks without user prompts. The same week, Nvidia released the Open Agent Safety Platform, comprising OpenShell, an open-source runtime that traces and enforces agent behavior, and Sentry, a watchdog running on separate BlueField 4 DPUs physically isolated from the agent process. The timing is notable because always-on agents eliminate natural human review checkpoints, leaving credentials persistently exposed and failures potentially silent. Nvidia's out-of-band design matters because a watchdog sharing the same processor as the agent could itself be manipulated by a misbehaving agent. However, Nvidia acknowledges the platform enforces predetermined boundaries rather than acting as a universal kill switch, meaning the quality of safety still depends on the policies humans write.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ERC-3643 Transfer Controls Can Be Tested for Permissioned Token Compliance

ERC-3643 permissioned tokens require verifiable transfer controls, and a structured approach using real token, registry, and compliance contracts can make those rules observable and testable. A recipient-country allowlist rule was implemented against the actual ERC-3643 contract suite and validated through 19 passing tests, including a deliberately broken module and its correction. The walkthrough highlights a key discrepancy between the ERC-3643 specification, which states minting bypasses compliance, and the pinned implementation, which calls canTransfer during minting — a difference teams must resolve before any issuance transaction. Each compliance requirement, such as identity claims, country restrictions, wallet freezes, and agent roles, is mapped to a specific enforcement point and an observable test assertion. The exercise, conducted in the context of blockchain engineering at Pharos Production, underscores that a general claim of compliance support is insufficient without explicit, testable contract behavior for integration engineers.

0 comments Read more at DEV Community