Who this is for
Publishers, independent developers, and small product groups who already have a utility app in use — flashlight, weather, file manager, alarm, calculator, VPN toggle, battery helper, QR reader, or a similar single-purpose app — and need to know where people stall inside its settings.
What you leave with
A written findings memo, an annotated control map, and a ninety-minute debrief. You leave knowing which labels were misread, which nested screens were never opened, and which changes people could not undo.
Scope
One utility app. We study either the full settings tree or a named area (for example notification quiet hours, unit preferences, or the reset path). Testers work from a build you provide. We do not rewrite the interface or ship code.
Included
- Intake call to agree the controls under study and the tasks testers will attempt
- A control map of labels, grouping, defaults, and reverse paths before sessions begin
- Recruitment of six to eight testers in the Klang Valley who already use a similar utility
- Facilitated sessions in English, Bahasa Malaysia, or Mandarin, as the tester prefers
- Annotated notes on hesitation, mis-taps, abandoned searches, and failed reversals
- A findings memo and a ninety-minute debrief with the people who commissioned the work
Not included
- Interface redesign, copywriting of new labels, or engineering changes
- Installation of tracking libraries or ongoing measurement after the study window
- Comparison against competitor apps unless agreed in the brief as a short appendix
- Testing of in-app purchases, accounts, or anything outside the settings tree
Who runs it
Sessions are facilitated by Control Vertex Hub in Petaling Jaya. Amira Hassan leads the study design. Wei Liang Tan runs most of the live sessions. Priya Nair writes the findings memo.
How the weeks run
-
Intake
You send the current build, a list of controls that worry you, and any known complaints. We agree the tasks testers will attempt and the languages we will run.
-
Control map
We walk every reachable setting, note the default, the label, the grouping, and how a person reverses the change. This map is the spine of the sessions.
-
Sessions
Each tester works through the agreed tasks on a phone we provide or on their own device if the build allows. We watch the hunt, not a scripted tour of every screen.
-
Findings and debrief
The memo groups what we saw by control, not by tester. The debrief is a conversation about what to change first, not a slide performance.
Time
Most audits take three to four weeks from a complete intake pack to the debrief. Recruitment of testers who already use a similar utility usually takes seven to ten days in the Klang Valley.
Where sessions happen
Sessions run at our room on Jalan 5/65 in Petaling Garden, or by screen-share when a tester cannot travel. Field visits inside Selangor are a separate study type.
What you prepare
Provide a sideloadable build or a store listing we can install, a short note on known problem controls, and a contact who can answer questions during the study week. Testers should not be your own staff.
Limits
We study settings interaction, not the whole app. Games, social networks, and banking apps sit outside this practice. We will not run sessions with children. Builds that require a work account we cannot obtain will delay the start.
How we price it
Quoted from RM 8,500 for one app and six testers. The figure moves with tester count, extra languages, a second settings area, or travel beyond Petaling Jaya. See the rates page for the factors we price against.
Next step
Send a brief through the contact form naming the app, the controls that concern you, and a window when a build will be available.