AQUILAintelligence

Field guide

Useful before you commission anything.

Short guides written to be useful whether or not you ever work with us. Take them to any studio.

Writing a one-page brief

A good brief is short. It answers five questions: what problem exists today, who has it, what would be different if it were solved, what constraints are fixed (dates, budget range, systems that must stay), and what you do not know yet. The last one is the most valuable; it tells a studio where to spend discovery time.

Avoid long feature lists at this stage. Features are answers; a brief should be mostly questions and facts.

Native, cross-platform or website?

Website

Reaches everyone, no store review, cheapest to maintain. Best when visits are occasional.

Cross-platform app

One codebase for iOS and Android. Good default for most apps with regular use.

Native apps

Two codebases, closest platform fit. Worth it for heavy device features or demanding performance.

What you should own at the end

Glossary

Discovery
Early work to understand the problem before committing to a solution.
MVP
The smallest version that tests whether the idea works with real users.
Wireframe
A low-detail layout showing structure without visual styling.
Prototype
A clickable model used to test flows before code is written.
Design system
Reusable components and rules that keep an interface consistent.
API
A defined way for two pieces of software to exchange data.
Staging
A private copy of the product used for testing before release.
CI/CD
Automation that tests and deploys code changes consistently.
Regression
Something that used to work and broke after a change.
Technical debt
Shortcuts that save time now and cost time later.
WCAG
The international guidelines for accessible web content.
Phased release
Releasing an update to a portion of users first.

Tool · illustrative

Signal or assumption?

The same triage as on the overview page, here for convenience. With optional storage accepted, your list is remembered on this device.