Edition 6 · Updated 25 September 2026AWST (UTC+8) · Retained fifth edition
KNOQ

INSIDE KNOQ · OUR PRODUCT RECORD

Product principles
and development history.

The idea we are building, the choices behind it, and the milestones we can substantiate.

KNOQ is being built to connect households and businesses that need local help with independent trades and service professionals who have the skills and time to offer it.

Both sides have a choice. A useful connection needs agreement.

THE PRINCIPLES

Useful for both sides.

01

Make room for choice

Homes and businesses choose the help they need. Independent professionals choose their availability, coverage and the requests that suit their business.

02

Respect the commitment

Availability starts the conversation. The professional proposes scope, price and timing; the customer explicitly accepts to confirm the booking. An assessment does not authorise repairs.

03

Keep privacy in the journey

Precise location sharing belongs to the active journey. Live travel progress stops at arrival, before completion or review.

04

Start local and learn

KNOQ starts in Hillarys and surrounding suburbs. Feedback from households, businesses and independent professionals helps shape the trial and what comes next.

Independent professionals set their own prices and remain responsible for their credentials, insurance and work. Optional memberships do not buy priority or guarantee work.

THE CONNECTED JOURNEY · TRIAL EXPERIENCE

From a need to an agreed next step.

This is the journey KNOQ is building and refining through the trial. Request choices are alternatives; the numbered stages describe how an agreed job progresses. Testing of the full journey continues across Android and iOS.

  1. A home or business describes the need

    Choose the service and ask for help soon, arrange a time, or request a quote first. Those are three ways to begin, not three steps every request must take.

  2. A professional considers the fit

    The professional chooses their available time and service area, reviews the request and decides whether the work fits. They can propose scope, price and timing, suggest another time or pass.

  3. Both sides agree what happens next

    During the trial, the customer explicitly accepts the professional’s scope, price and timing to confirm the booking, subject to eligibility and availability. An assessment has its own agreed scope, timing and any fee; repairs need a separate proposal and agreement. If nobody suitable is available, another time can be explored.

  4. Location follows the commitment

    Before the customer accepts the proposal, the job location is approximate. Booking confirmation releases the exact address to the booked professional. During the free trial, KNOQ fees are waived and customers pay professionals directly for agreed work.

    See the current trial and pricing explanation for the applicable stage and conditions.

  5. Travel progress ends at arrival

    The customer can follow the booked professional’s travelling status until arrival. Both apps use KNOQ’s Mapbox style, with route and estimated-arrival information where available. Professionals can choose a vehicle or animal journey marker. The marker is a visual choice, and an arrival estimate is not a guarantee. Live-trip sharing stops at arrival.

  6. The work is checked, then reviewed

    The journey continues through checking the work, confirming completion and leaving feedback tied to that KNOQ job. These stages remain part of ongoing end-to-end trial testing. Completion and review do not extend live-trip sharing.

Availability and timing depend on suitable local supply and professional confirmation. For a question, correction or help getting started, contact KNOQ Support.

Watch or read the existing explanation

The 90-second film and transcript and four concept films with captions and transcripts illustrate the service journey. They are explanations, not recordings that prove a complete live job.

CLEAR STATUS

What the demonstrations mean.

Public today
Household and professional account creation, enquiries and optional expressions of interest. Creating an account does not book a service or approve a professional.
Journey and illustrations
The request-to-review journey above is the trial workflow being tested and improved. Concept films and phone-shaped illustrations explain it; they do not certify that every step has passed on every device.
Development demonstrations
The website labels its Android completion and review screens as development screens, not live job information. They do not establish that the full journey is operational.
App and account service
The current app privacy notice covers website account creation, app access, professional assessment, consent-based notifications and location sharing. Online account deletion and email requests are available. Payments in KNOQ remain disabled. Public downloads are awaiting store approval.

TRADE MARK STATUS · UPDATED 21 SEPTEMBER 2026

Accepted early; registration pending.

IP Australia examined and accepted Australian trade mark application 2695639 for the KNOQ word mark in Classes 9 and 35 on . KNOQ is not yet a registered trade mark.

Publication comes next
IP Australia says it will publish acceptance after and send a further acceptance notice. This is not a registration date.
Time for opposition
The two-month opposition period starts when acceptance is published. It has not started with this early-acceptance letter; the exact dates are still to be confirmed.
Registration remains pending
Registration can follow if no opposition is filed, or any opposition is overcome. The letter states that registration cannot occur earlier than 7.5 months after filing on 10 September 2026. No registration date is guaranteed.

Source: IP Australia’s letter dated 21 September 2026, “Your trade mark application has been accepted early”. The original correspondence is retained privately. View application 2695639 on Australian Trade Mark Search.

RECORDED MILESTONES

A dated account, with clear limits.

From the first idea on 16 August to account signup and public app-store submissions on 25 September, this record follows KNOQ’s development. Each milestone describes what was achieved at the time; earlier limitations are historical, not today’s status.

An idea found its name and a home

The marketplace concept was taking shape in a ChatGPT conversation titled Assist app concept. Early working names included Assist and Ping. By late afternoon, a KNOQ business-name application had been submitted and knoq.au had been successfully registered.

That same day, the first KNOQ website — a simple coming-soon page for private sharing — reached its first Netlify production deploy at approximately 4:58 pm AWST. Its browser title was KNOQ — Coming soon, and it opened with the line Help nearby. Right when it matters.

The site was configured for knoq.au, but DNS and TLS were still propagating. The time above is therefore the first hosting-deployment time, not proof of the exact instant knoq.au became publicly reachable.

That makes 16 August the first substantiated KNOQ day in this record: an idea becoming something named, visible and ready to build. It is not a claim about the exact moment the name was coined.

KNOQ became a registered business name

By 18 August, KNOQ’s registered business-name status had been published on the website. KNOQ is a registered business name operated by Steve Harley under his ABN; it is not a separate company.

The first product foundations

Repository history records the first KNOQ Android and API foundation on 21 August, followed by the native iOS foundation on 22 August.

These were development foundations, not evidence that a public marketplace was operating.

Three Australian domains secured

knoq.com.au and knoq.net.au were both successfully registered. Together with knoq.au, this created KNOQ’s three-domain Australian home.

Domain registration secures web addresses. It does not establish trade mark rights or exclusive rights to a business concept.

Official public website and expressions-of-interest launch

Password protection was removed from the public website pages. KNOQ’s preserved release-check records show successful anonymous access checks at approximately 5:06 pm AWST (UTC+8).

This milestone concerns the website and expressions of interest. Household bookings were still coming soon.

The check time is not the exact instant the password was removed.

Trade mark application lodged and this record expanded

KNOQ lodged Australian trade mark application 2695639 for the plain word mark KNOQ in Classes 9 and 35. At lodgement, the application awaited examination by IP Australia. See the current trade mark status. Lodged does not mean registered.

The first edition of this product record was prepared and published on 10 September. Edition 2 expanded the dated account with the substantiated origin, domain, first-hosting and product-foundation milestones above.

Safer foundations, tested across both apps

KNOQ strengthened the private-preview foundations across Android, iOS and the connected service. Testing covered clearer quote and cancellation recovery, protected address selection, travelling-status safeguards and matching behaviour across both native apps.

The routing work remains deliberately dormant. Address selection uses an opaque, short-lived receipt, and any future route result is designed to be encrypted and expire. Provider-backed road routing, traffic-aware arrival estimates and turn-by-turn navigation are not active.

Android Build 163 was signed locally but not uploaded. iOS Build 163 was source-frozen but not archived. Payments, operational account deletion, public marketplace access and guaranteed professional availability remain closed. This records verified development progress, not a public product launch.

KNOQ trade mark application accepted early

IP Australia confirmed that application 2695639 for the KNOQ word mark in Classes 9 and 35 had been examined and accepted early. This is an examination milestone; the trade mark is not yet registered.

Publication of acceptance will follow after 10 February 2027, with the opposition stage before registration. Read the current status and next steps.

Maps, personal journey markers and online account deletion

Both native apps gained the approved Mapbox look and professional choice of vehicle and animal journey markers, including for trial professionals. Online account deletion became available alongside the email support route, with progress and retention explained in the app privacy notice.

These milestones concern specific app and account capabilities. They do not establish that every real-job journey has passed from request to review.

Account signup opens and both apps enter public review

Households and professionals can create a shared KNOQ account online. Steve has secure access to review professional applications for each service. Android 238 and iOS 204 were submitted to their public stores; all ten active devices were verified on those builds. Store approval and wider live-job acceptance are separate milestones.

The free trial has no published end date and does not automatically become a paid plan. The website and Ask Norb were updated to explain current signup, professional assessment, account services and pending public app downloads. Further cross-platform journey testing remains in progress.

NATIVE APP DEVELOPMENT · FOUNDATION SPRINTThe apps take shape.21 August–10 September 2026 · 10 milestones across Android and iOS

In nineteen days, two native applications moved from foundations to privately tested release candidates. The record below celebrates that pace without calling a development build a public launch.

iOSAndroid™KNOQ-designed markers · no Apple or Google endorsement implied
  1. Android

    Android development begins

    KNOQ’s first native Android foundation was committed in Kotlin and Jetpack Compose. Separate development and staging environments followed immediately.

  2. iOSAndroid

    iOS joins the build

    The native Swift and SwiftUI foundation arrived the following morning. Authentication, customer and professional journeys, notifications and travelling-location behaviour began converging around a shared API contract. A platform-parity release gate was established the same day.

  3. Android

    The first shareable app

    An early Android staging build—KNOQ Version 9—was distributed privately through Firebase App Distribution. Request creation and authoritative live-trip mapping then became working parts of the Android development journey.

  4. iOSAndroid

    From prototypes to controlled releases

    iOS reached scenario parity, an isolated Google Play internal build was prepared, and both applications gained stronger arrival-assurance, verification and fraud-control foundations.

  5. NORBiOSAndroid

    Norb is born

    Norb was introduced across the native applications as KNOQ’s service guide. Ask Norb entered staging, followed by the approved V8 character and waiting-animation package. This is the strongest evidence-backed date for Norb’s introduction.

  6. iOSAndroid

    Real devices, matched experiences

    The Mac Mini became KNOQ’s authoritative iOS build host. Scheduling, cancellation, visual parity and the live-trip privacy lifecycle were exercised across physical Android and Apple devices—including ending precise location sharing on arrival.

  7. iOSAndroid

    Messaging, notifications and navigation

    Protected messaging, iOS push notifications and appointment recovery matured across both platforms. The iOS journey gained native Apple Maps handoff while continuing to protect the active travel-location session.

  8. iOSAndroid

    The complete service journey takes shape

    Testing expanded across phones and tablets. Quote review, competing acceptances, work agreements, invoices, visit timing and encrypted visit details were added. A Stripe sandbox foundation was created but remained deliberately dormant—not a live payment service.

  9. iOSAndroid

    Private production preview

    Recovery and support controls were strengthened, a private Google Play testing link was issued, and signed iOS production candidates were archived. iPad support, Apple privacy declarations and later Android candidates followed. These were private testing and store-readiness milestones—not public store launches.

  10. MAPSiOSAndroid

    The Mapbox foundation is laid

    KNOQ’s Mapbox account was secured, a Signal Noir map style was published, restricted development credentials were prepared and an address-integration package was completed. Native integration and device verification were still pending, so this records the Mapbox foundation—not completed app integration.

Apple, App Store and iOS are trade marks of Apple Inc. Android and Google Play are trade marks of Google LLC. Platform names are used only to identify KNOQ’s development work. The device markers are KNOQ artwork, not platform logos or store badges.

Evidence for the added milestones comes from dated source-thread, repository, hosting and account correspondence. Private receipts, reference numbers, addresses, tester identities, credentials and billing details are not published. Development and earlier sharing preceded the official launch. This record does not establish the earliest date on which any KNOQ idea or feature became public. Historical dates above refer to the events described, not the publication date of this page.

EDITIONS AND CORRECTIONS

A record that can be followed.

Edition 6 · updated (AWST). Updates the current stage, trial journey, maps, professional marker choice, account signup, assessment and deletion milestones. Records Android 238 and iOS 204 submission and device delivery separately from public store approval and full journey acceptance. Earlier dated milestones and retained editions remain available below.

Edition 5 · first published (AWST). Records IP Australia’s early acceptance of KNOQ application 2695639, distinguishes acceptance from registration and explains the later publication and opposition stages. Read the retained fifth edition.

Update prepared 16 September 2026. Read the retained update. Clarifies the planned initial-trial agreement, assessment, address-release and direct-payment sequence. These are approved design requirements, not a claim that the marketplace is open. The recorded milestones and earlier editions below are unchanged. Read the short trial guide.

Edition 4 · first published (AWST). Added the verified Build 163 development milestone, including protected address and travelling-progress foundations, cross-platform qualification and the capabilities that remain inactive. Read the retained fourth edition.

Edition 3 · first published (AWST). Added the expandable native-app foundation sprint, ten evidence-backed Android and iOS milestones, KNOQ-owned platform markers and clear trade-mark and capability limits. Read the retained third edition.

Edition 2 · first published (AWST). Expanded the dated account with KNOQ’s first substantiated day, registered business-name status, domain portfolio, first website deploy, product foundations and pending trade-mark application. Read the retained second edition.

Edition 1 · first published (AWST). Prepared on 10 September 2026. Read the retained first edition.

Later material changes will identify what changed and retain earlier public editions where privacy and rights permit. A correction will distinguish a corrected historical fact from a new product development.

This page records KNOQ’s product approach and history. It makes no claim of exclusive rights over the marketplace concept. To suggest a correction, contact KNOQ Support and identify the passage and supporting information.

Founded and owner-operated by Steve Harley.

Steve is KNOQ’s Founder & Venture Architect and remains accountable for its direction. KNOQ is a registered business name operated by Steve Harley, ABN 40 673 535 778.

Read about Steve and the purpose behind KNOQ