featkpr, in two minutes

A short, plain version of this site, for anyone. Every link below opens the part of the site that goes deeper.

Every web app is a set of features
Sign in, create a book, share a page, delete an account. People move through them in flows, to reach a goal.
Almost nobody has that written down
It lives in people's heads. Documents fall out of date, and tests only check the app one screen at a time.
featkpr draws the map
It reads the app's code and walks a running copy, then writes down the features, how they lead into each other, the flows people take and the goals they reach.
Your team checks it, one question at a time
Keep it, drop it, or say it better. Each answer is kept, with who gave it and when.
Everything else is built on the checked map
Tests, checks of who may do what, what a code change touches. Later: analytics, feature flags, a user guide.

The words, from smallest to largest #

FeatureGoalFlowFeatures group goals, and flows end on goals.

Feature: one thing the app lets a person do, named from its code. On BookStack: “View page revision history”.
Goal: a change a person makes, or something they read, with what must hold around it: who may do it and what must be refused. Kept under the feature on whose routes it sits. On BookStack: “Create a book”.
Flow: how a person moves through the app, screen by screen, across one or more goals. On BookStack: “Delete an API token”, six screens from the home page to the delete page.
The map: all three for one app, and how they connect
The review: a person keeping, dropping or rewriting what featkpr drafted

Half an hour with Tim, on BookStack, your questions first.