# Arlez blog

Plain-text mirror of https://arlez.app/blog. Every article below is also
published as Markdown at the address shown.

## What a product inbox is, and what it is not

- Address: https://arlez.app/blog/what-a-product-inbox-is.md
- Page: https://arlez.app/blog/what-a-product-inbox-is
- Published: 2026-08-18
- Topic: Support

A support desk closes tickets. A tracker holds work. A product inbox is the thing between them, and most small teams are missing it.

## Reports are conversations. Product issues are the work.

- Address: https://arlez.app/blog/reports-and-product-issues.md
- Page: https://arlez.app/blog/reports-and-product-issues
- Published: 2026-08-14
- Topic: Practice

Why Arlez keeps two different objects instead of one, and what goes wrong when a tool only has one.

## Triage without building a queue you will come to dread

- Address: https://arlez.app/blog/triage-without-a-queue.md
- Page: https://arlez.app/blog/triage-without-a-queue
- Published: 2026-08-11
- Topic: Practice

Three states, one pass a day, and no backlog that grows in the dark.

## Your first week of customer feedback

- Address: https://arlez.app/blog/first-week-of-feedback.md
- Page: https://arlez.app/blog/first-week-of-feedback
- Published: 2026-08-06
- Topic: Support

What actually arrives when you put a feedback button in a product, and what to do with it.

## Five people reported the same thing. Now what?

- Address: https://arlez.app/blog/duplicate-reports.md
- Page: https://arlez.app/blog/duplicate-reports
- Published: 2026-08-01
- Topic: Practice

Duplicates are not noise to be closed. They are the strongest signal in the inbox, if you keep them attached.

## In-app support for an iOS app, in an afternoon

- Address: https://arlez.app/blog/in-app-support-for-ios.md
- Page: https://arlez.app/blog/in-app-support-for-ios
- Published: 2026-07-28
- Topic: Apple

Adding ArlezKit to a SwiftUI app: a package, one configure call, and a sheet.

## A support sheet that belongs in the app it is in

- Address: https://arlez.app/blog/support-sheet-in-swiftui.md
- Page: https://arlez.app/blog/support-sheet-in-swiftui
- Published: 2026-07-23
- Topic: Apple

Why a web view is the wrong answer on Apple platforms, and what a native support surface has to get right.

## One download, three platforms — shipping Arlez on iPhone, iPad and Mac

- Address: https://arlez.app/blog/one-app-three-platforms.md
- Page: https://arlez.app/blog/one-app-three-platforms
- Published: 2026-07-17
- Topic: Apple

What a shared SwiftUI codebase actually shares, where it has to diverge, and why the App Store listing stayed one listing.

## App Review, support URLs, and the link Apple checks

- Address: https://arlez.app/blog/app-review-and-support-urls.md
- Page: https://arlez.app/blog/app-review-and-support-urls
- Published: 2026-07-11
- Topic: Apple

Every App Store listing needs a support URL that works. Here is what "works" means, and how to have one before you have a support site.

## Push notifications a founder actually wants

- Address: https://arlez.app/blog/push-notifications-for-founders.md
- Page: https://arlez.app/blog/push-notifications-for-founders
- Published: 2026-07-07
- Topic: Apple

Most feedback tools notify you about everything, so you turn them off. A better default is to notify about the two things that decay.

## One public ID in the app, one secret key on the server

- Address: https://arlez.app/blog/product-id-vs-api-key.md
- Page: https://arlez.app/blog/product-id-vs-api-key
- Published: 2026-07-02
- Topic: Integrations

Arlez has two credentials that look similar and are opposites. Getting them the wrong way round is the only way to hurt yourself with it.

## Putting a feedback button on a site you did not build in a framework

- Address: https://arlez.app/blog/web-launcher-on-a-marketing-site.md
- Page: https://arlez.app/blog/web-launcher-on-a-marketing-site
- Published: 2026-06-26
- Topic: Integrations

Two lines of HTML, one thing you must configure first, and the four failures worth handling.

## A support page for a product that has no app

- Address: https://arlez.app/blog/hosted-forms-without-an-app.md
- Page: https://arlez.app/blog/hosted-forms-without-an-app
- Published: 2026-06-20
- Topic: Integrations

Hosted forms cover the cases an SDK cannot reach — an App Store listing, a printed card, an email signature, a QR code on a device.

## Turning a support mailbox into structured reports

- Address: https://arlez.app/blog/email-intake.md
- Page: https://arlez.app/blog/email-intake
- Published: 2026-06-16
- Topic: Integrations

Email is where feedback already is. Forwarding it into a project keeps the conversation and stops the second inbox.

## Getting a report into the tracker you already use

- Address: https://arlez.app/blog/webhooks-and-your-tracker.md
- Page: https://arlez.app/blog/webhooks-and-your-tracker
- Published: 2026-06-11
- Topic: Integrations

Arlez does not want to be your issue tracker. Here is how work leaves it, and what should not.

## Is this integration actually wired up?

- Address: https://arlez.app/blog/is-this-project-live.md
- Page: https://arlez.app/blog/is-this-project-live
- Published: 2026-06-05
- Topic: Integrations

Every project reports which channels have called Arlez, and it does not wait for a first report to say so.

## What to attach to a bug report, and what never to

- Address: https://arlez.app/blog/what-to-attach-to-a-bug-report.md
- Page: https://arlez.app/blog/what-to-attach-to-a-bug-report
- Published: 2026-05-29
- Topic: Support

The context that makes a report reproducible is small and specific. Everything else is a liability you now have to protect.

## Feedback is personal data. Treat it that way.

- Address: https://arlez.app/blog/feedback-is-personal-data.md
- Page: https://arlez.app/blog/feedback-is-personal-data
- Published: 2026-05-22
- Topic: Privacy

A bug report has a person in it. What that means for storage, access, deletion, and the awkward case where the data is not yours to give back.

## Bring your own AI key, and why we did it that way

- Address: https://arlez.app/blog/bring-your-own-ai-key.md
- Page: https://arlez.app/blog/bring-your-own-ai-key
- Published: 2026-05-15
- Topic: Privacy

The alternative was bundling model costs into a subscription. That would have been simpler for us and worse for you.

## What Arlez sends to a model, and what it never does

- Address: https://arlez.app/blog/what-arlez-sends-to-a-model.md
- Page: https://arlez.app/blog/what-arlez-sends-to-a-model
- Published: 2026-05-08
- Topic: Privacy

If AI features touch your customers' words, you are owed a precise answer about which words, when, and where they go.

## Letting an agent work your inbox

- Address: https://arlez.app/blog/letting-an-agent-work-your-inbox.md
- Page: https://arlez.app/blog/letting-an-agent-work-your-inbox
- Published: 2026-05-01
- Topic: Automation

A scoped key, a narrow job, and the two things you should never delegate.

## Closing the loop after a release

- Address: https://arlez.app/blog/closing-the-loop-after-a-release.md
- Page: https://arlez.app/blog/closing-the-loop-after-a-release
- Published: 2026-04-24
- Topic: Practice

The step almost every team skips is the cheapest retention work available, and it takes one action if the links are already there.

## Release notes that answer the people who asked

- Address: https://arlez.app/blog/release-notes-that-answer-people.md
- Page: https://arlez.app/blog/release-notes-that-answer-people
- Published: 2026-04-17
- Topic: Practice

Most release notes are written for nobody. Written for the reports that drove the release, they do two jobs at once.

## Saying no to a feature request without losing the customer

- Address: https://arlez.app/blog/saying-no-to-a-feature-request.md
- Page: https://arlez.app/blog/saying-no-to-a-feature-request
- Published: 2026-04-10
- Topic: Support

The damage is not done by the no. It is done by the year of silence that preceded it.

## A support routine for one person

- Address: https://arlez.app/blog/a-support-routine-for-a-solo-founder.md
- Page: https://arlez.app/blog/a-support-routine-for-a-solo-founder
- Published: 2026-04-03
- Topic: Support

Twenty minutes a day, one hour a month, and nothing that depends on remembering.

## From feedback to a roadmap you can defend

- Address: https://arlez.app/blog/from-feedback-to-a-roadmap.md
- Page: https://arlez.app/blog/from-feedback-to-a-roadmap
- Published: 2026-03-27
- Topic: Practice

Counting reports is not a roadmap. But a roadmap with no counting in it is just your preferences with a schedule attached.
