Every company I have worked with carries the same invisible debt: somewhere between thirty and three hundred spreadsheets nobody versions, fed by manual exports from four different systems, and yet feeding credit decisions, capacity plans and the monthly close. The September 1, 2026 announcement — building apps in Amazon Quick by describing them in natural language — aims squarely at that debt. The risk is trading an ungoverned spreadsheet for an ungoverned app, now with a write connector and an AWS invoice attached. So I did not write a feature review: I wrote the bake-off I would run before approving the first app, across the four routes that genuinely compete for this work.

What the September 1 GA actually ships

The Apps in Quick documentation says more than the announcement does. Seven capabilities matter architecturally: conversational authoring (the agent writes the code while you watch), live Quick Sight visual embeds inside the app, action connectors that call external APIs, built-in foundation-model inference for summarisation and classification, reading documents from spaces, persistent key-value storage across sessions, and one-click publishing under Quick's SSO.

Read that combination again: action connectors plus persistent key-value storage. This is not a prettier dashboard. It is an application with its own state and a write path into third-party systems, authored by conversation and published with one click. In a financial-grade environment, that is precisely the class of artefact a change board expects to see with an owner, a version and a rollback.