Practice
A small review studio on Jalan Padi Ria, not a platform.
System Fabric Path exists to sit with installed mobile applications and write down what is actually happening — before a partner go-live, after a complaint, or when a release date is already on the wall.
The name is a trading name, not a product. We do not sell software, dashboards, or a monthly scan. We take a scoped week (sometimes two), work from the builds you provide, and return a findings memo with a walkthrough. If the work needs a retest, that is scheduled in writing.
Johor Bahru is the right place for this. Product teams here ship for Malaysian residents, for people who cross to Singapore, and for regional operations that still have to behave on a mid-range Android in Tebrau traffic. We keep the studio in Bandar Baru Uda so a briefing can be a conversation in a room, not only a call.
What we will and will not do
We review iOS and Android applications. We will look at companion APIs only as far as the client on the phone depends on them. We do not run a 24-hour monitoring service, we do not take over your store accounts, and we do not press submit on your behalf.
We are not a law firm. Privacy notes describe product behaviour against your notice and against ordinary PDPA themes such as purpose and access. Legal conclusions stay with your counsel.
People who write the memos
Reviewers you can name in a kickoff
-
Aisha Rahman
Lead reviewer
Aisha sets the scope for each engagement and writes the findings memo. She spent years inside product teams before moving to independent review work in Johor Bahru.
-
Daniel Tan
Security and privacy
Daniel spends most of his week on device storage, session handling, and SDK inventories. He prefers a reproducible note over a dramatic finding.
-
Mei Ling Ong
Assistive use and performance
Mei Ling runs VoiceOver and TalkBack journeys and keeps a small shelf of mid-range Androids that resemble what people actually carry in Johor.
Working with in-house teams
Most of our weeks are booked by a product owner or an engineering lead who already has a backlog. We fit around that. You keep the repositories. We keep copies of the artefacts only for the engagement and the retest window, then we delete them according to the terms.
If you want to see the path of a typical week before you write, the method page is the honest version. If you already know the review you need, start from the list of reviews or write to the studio.