Can my app make QR codes, for tickets or check-in?
Short answer
Yes: your AI coder can make QR codes in your app; a published app cannot use the camera, so scan with a phone's camera.
Deeper
A QR code is a square pattern that a phone's camera reads, often holding a web address.
What GilbPlatform does today. GilbPlatform, the service that keeps your vaults, has no ready-made QR codes, tickets or check-in for your app.
Making QR codes. Agent.Coder, the agent that writes your app's code, can make a QR code in the person's browser, with a small program kept in your app's own files, and show it as a picture on the page or in a PDF ticket. The rules of a published app let it show pictures it makes itself in the page. What a code holds is up to your plan, such as the web address of a ticket in your app. Tell Kai-Zen, the planning agent, what each code should open.
What is blocked today. When your app goes live, at https://<name>.pages.dev, a web address of its own, GilbPlatform sets the rules that address serves your app with, and you cannot change them. They switch off the camera and the microphone, so your published app cannot scan a QR code itself. They also let it run only its own scripts and fetch data only from its own address and from GilbPlatform's own addresses, such as id.gilb.com, so a QR or ticket service from another company cannot be added today. If you need the app itself to scan, write to [email protected].
What still works. A phone's own camera can scan. Apple says: "You can use Camera or Control Center to scan Quick Response (QR) codes for websites, apps, coupons, tickets, and more." (https://support.apple.com/guide/iphone/scan-a-qr-code-iphe8bda8762/ios, read 13 November 2026). If the code holds an address in your app, the phone offers to open it.
Check-in. Your AI coder could build a check-in screen that a ticket's address opens, where a signed-in person you gave access to marks the ticket as used. The ticket is then a record, one piece of data with its own address, in a vault, the place where a person or a group keeps their records. Showing or hiding a screen does not protect the data. What a person may read or write is decided by GilbPlatform, from the access they were given, not by your app's screens: your app gets no more than the signed-in person can. So give Write + Read on that vault only to the people who check tickets; it lets them change and delete every ticket in it, not only mark one as used. A QR code can be copied like any picture, so ask your AI to make the app refuse a ticket that was already used. This works only in a published app that people sign in to: a published website that signs no one in cannot read or write in vaults, because GilbPlatform answers the pages of an app, not of a website.
This answer is written for a computer screen.
Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:21 and :146 (a functions folder refused: a functions folder would run your code on the server), :165-172 (the headers every published site gets: Content-Security-Policy default-src 'self'; script-src 'self'; img-src 'self' data: blob: https://*.gilb.com; connect-src 'self' https://*.gilb.com; form-action 'self'; Permissions-Policy camera=(), microphone=(), geolocation=()). MDN, frame-src (falls back to child-src, then default-src), https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-src, read 13 November 2026. Apple, Scan a QR code with your iPhone camera, https://support.apple.com/guide/iphone/scan-a-qr-code-iphe8bda8762/ios, read 13 November 2026. Live help pages: Can my app have different kinds of users, such as admins and members? (showing or hiding a screen does not protect the data); Can my app connect to other services, such as weather, shipping, maps or calendars? (the same rules switch off the browser's own location).
Checked against GilbApp d529620.