Scenario: Evaluate the primary personal remote-access workflow before considering optional remote access.
- Install the Mac companion and open AirDesk on the iPhone or iPad.
- Use local discovery, pair the devices, and select the Mac display.
- Test direct touch, pointer movement, typing, and reconnection on the same trusted network.
What success looks like: The Apple device discovers and controls the intended Mac with a clear pairing boundary and usable display interaction.
Boundary: This does not evaluate enterprise fleet administration, Windows control, or unattended help-desk workflows.
Additional public evidence: apps.apple.com
Review AirDesk facts and availability
Scenario: Use a normal walk or run to assess the local-first journaling workflow.
- Record a short activity and add only the permissions and details you are comfortable sharing with the app.
- Add a note, mood, photo, or personal track that is useful for remembering the session.
- Review the saved activity and confirm the history is understandable later.
What success looks like: The activity, route context, and personal notes form a useful private record on the user’s device.
Boundary: Carmen is a personal journal, not medical diagnosis, treatment advice, or emergency monitoring.
Additional public evidence: apps.apple.com
Review Carmen Health facts and availability
Scenario: Use synthetic project data to evaluate whether one operational workflow can replace disconnected email and spreadsheets.
- Define a sample lot, client, selection or change request, responsible trade, and required approval.
- Walk the request through status, document, communication, and deficiency or handover checkpoints.
- Review what each role needs to see and identify any company-specific rules before implementation.
What success looks like: The builder can see a coherent path from request to completion and can identify where configuration is needed.
Boundary: Developer Hub is delivered through implementation discovery; it is not an instant self-serve accounting or payroll app.
Scenario: Use a fictional private training academy to evaluate how HelloX Campus carries one student record from applicant intake through enrolment, scheduling, attendance, teaching activity, documents, and compliance preparation.
- Create a fictional applicant and convert the record into an enrolled student without re-entering core contact and program information.
- Schedule a class, record attendance, and review the same student context from the teacher workflow.
- Prepare a fictional readiness report or workbook and confirm that validation issues are visible before staff handoff.
What success looks like: The fictional student keeps one consistent identity across the selected workflows, staff can identify the next action without technical training, and the prepared output clearly distinguishes validation from official submission.
Boundary: Use synthetic data only. The evaluation does not demonstrate regulator approval, automatic government-portal access, or coverage of every requirement that may apply to a school.
Scenario: Use a safe demonstration page to evaluate the real mark, comment, and submission workflow without adding the reporter to a Delivery Hub project.
- Open Feedback and confirm that page marking is active immediately.
- Click one exact page area, choose Problem, Idea, or Question, and add a short non-sensitive comment.
- Submit the feedback and confirm that the receipt appears while the marker, screenshot, page URL, and comment stay together for project review.
What success looks like: A reporter can submit clear visual context in seconds without receiving Delivery Hub membership, while the project team receives enough information to review and triage it.
Boundary: Anonymous or host-authenticated reporting does not grant Delivery Hub access; only authorized project members can review, triage, and handle the submitted feedback.
Additional public evidence: youtube.com
Review HelloX Feedback facts and availability
Scenario: Evaluate common Mac-native Dataverse work in a non-production environment.
- Connect a test or development Dataverse environment with an appropriately limited account.
- Browse one table’s metadata and build a read-only FetchXML query with a small result limit.
- Review the results and the app’s scan or confirmation boundaries before testing any write or deployment tool.
What success looks like: A Mac user can inspect metadata and query test data without needing a Windows virtual machine.
Boundary: The evaluation does not claim the full XrmToolBox plug-in ecosystem and should not begin with destructive production changes.
Additional public evidence: apps.apple.com, youtube.com
Review Dataverse Studio facts and availability
Scenario: Assess whether meetings, source tasks, flagged email, and manual work fit the day’s actual capacity.
- Load or enter today’s meetings, tasks, and one piece of manual work.
- Estimate effort, reserve personal constraints, and split an item that is too large for the remaining day.
- Review the capacity result and export a report if a shareable record is useful.
What success looks like: The final plan makes overload visible and shows a credible set of work that fits the day.
Boundary: Effort Plan is an individual planning tool, not enterprise portfolio management, payroll, or team timesheet processing.
Additional public evidence: effortplan.com, hellox.ca
Review Effort Plan facts and availability
Scenario: Evaluate a focused native document workflow without opening a large development environment.
- Open a copy of a safe Markdown file containing headings, a list, a table, and a code block.
- Switch between reading, direct editing, and split preview while making a small change.
- Save the Markdown copy and test one supported export format.
What success looks like: The file remains readable and editable, and the exported document preserves the important structure.
Boundary: GoPlain is not a collaborative documentation host or a full programming IDE.
Scenario: Evaluate HelloAI as a collection by choosing the exact utility needed rather than judging it as one monolithic application.
- Choose one current document, image, QR, Markdown, or file-transfer tool on HelloAI.
- Use non-sensitive sample content and complete the tool’s stated workflow.
- Verify the result, review any privacy or processing explanation, and remove temporary content when the tool supports it.
What success looks like: The selected utility completes its narrow task without requiring a large software installation.
Boundary: Capabilities and data handling vary by tool; HelloAI is not a single offline enterprise suite.
Additional public evidence: helloai.ca
Review HelloAI facts and availability
Scenario: Define the evidence PocketABC must provide before it is recommended as an available product.
- Wait for a public testable release; the current page is a development preview only.
- At release, test one listening prompt, a timed spoken reply, tone feedback, and recovery after getting stuck.
- Confirm the feedback is understandable and that repeated practice improves response comfort without claiming certified test outcomes.
What success looks like: A released build demonstrates the promised spoken-performance loop with clear limits and repeatable practice.
Boundary: PocketABC is not currently downloadable and should not be listed or recommended as an available app.
Scenario: Compare the bundled offline workflow with optional online enhancement using non-sensitive text.
- Disconnect from the network and translate several ordinary English and Chinese phrases using the bundled dictionary.
- Test the system shortcut or browser extension with non-confidential text.
- Reconnect and compare optional rephrasing, noting where professional translation is still required.
What success looks like: Core lookup remains useful offline and optional enhancement is clearly separated from the bundled dictionary.
Boundary: XTranslator does not provide certified legal, medical, or contractual translation.
Scenario: Use a sandbox project and non-sensitive sample defect to evaluate the capture-to-ticket workflow.
- Import a test work item or enter safe ticket context from a non-production Azure DevOps project.
- Capture the problem as a screenshot or short recording and annotate the exact failure area.
- Review the generated bug details and create it only in the sandbox project.
What success looks like: The resulting bug includes enough context and visual evidence for another person to reproduce and triage it.
Boundary: XShot documents defects; it does not execute automated regression tests or replace Azure DevOps.
Scenario: Use the public sample set to evaluate difference review without exposing private documents.
- Open the built-in or public left and right sample files or folders.
- Review added, removed, and modified content and use manual alignment where it improves the comparison.
- Export a PDF report and verify that another reviewer can understand the differences.
What success looks like: The comparison makes meaningful changes visible and produces a clear local report.
Boundary: XCompare is not Git hosting, binary reverse engineering, or real-time collaborative editing.
Additional public evidence: hellox.ca
Review XCompare facts and availability
Scenario: Evaluate a practical local image-editing task with a non-sensitive source image.
- Open a copied sample image and remove or erase part of the background.
- Add one shape, annotation, or drawing mark and confirm selection behavior.
- Export a transparent PNG and inspect the result in another viewer.
What success looks like: The exported image preserves the intended transparency and visible annotation.
Boundary: XPainter is a focused local editor, not a cloud design system or advanced professional illustration pipeline.
Scenario: Use duplicated sample PDFs so the original documents remain untouched.
- Open copies of two safe PDFs, edit a small text field or fill a form, and add a test signature if appropriate.
- Merge the copies, reorder one page, and review the page sequence.
- Export the finished PDF and verify text, pages, form content, and signature appearance in another viewer.
What success looks like: The local output contains the intended edits and page order without requiring cloud document processing.
Boundary: Complex fonts and layouts may vary, and Xpdf is not an enterprise records, retention, or approval system.
Scenario: Compare the standard landlord workflow with the tailored Pro path without exposing tenant or customer information.
- Create a fictional property, unit, tenant, maintenance request, and follow-up deadline in a demonstration environment.
- Walk the request through communication, status, notes, documents, and completion.
- Identify whether the standard workflow fits or whether company roles, approvals, owner reporting, or service rules require Rental Smart Pro.
What success looks like: The team can see where routine rental administration becomes clearer and which company-specific requirements need implementation discovery.
Boundary: Use synthetic data for evaluation; Rental Smart Pro is tailored through discovery and is not an instant one-size-fits-all deployment.
Additional public evidence: apps.apple.com
Review Rental Smart facts and availability
