Show inspectors in the app whether a job is Spectora or Attik so they know where to complete it and see office notes

Objective

  • Show inspectors in the Attik mobile app a clear indicator of whether a job is a Spectora job or an Attik job so they know where to open office notes and where to complete the job.
  • For Spectora jobs, do not allow completing the job in the Attik app so inspectors are directed to complete the job and see office notes in Spectora.
  • Reduce wrong-place completions and confusion during the transition when both job types exist.

Background

  • Product feedback: inspectors are unsure whether to use Spectora or the Attik app for a given order when both types of jobs appear in the app. Without a visible distinction, they can complete in the wrong place or miss office notes.
  • The requirement is to (1) surface job type (Spectora vs Attik) in the inspector app and (2) block completion in the app for Spectora jobs so the correct system is used per job.

Scope

Mobile (Attik mobile app)

  • The inspection detail screen lives in app/(app)/inspection/[id].tsx and uses useInspectionDetails(id) from hooks/useInspectionDetails.ts. This screen is the primary place to show the job-type indicator and to gate completion for Spectora jobs.
  • Job-type indicator: Add a visible indicator (e.g. badge, label, or banner) that the job is "Spectora" or "Attik" so inspectors know where to go for office notes and completion. How job type is represented in the API (e.g. slug, report source, or inspection flags) is for the dev to determine from existing backend/API patterns.
  • Completion gating for Spectora jobs: For jobs that are Spectora, do not allow the "complete job" (or equivalent) action in the Attik appโ€”hide it, disable it, or replace it with guidance to complete in Spectora. Ensure the flow is consistent with where office notes are shown (Spectora for Spectora jobs).
  • Any schedule or list that links to the inspection detail should remain usable; the change is focused on the detail screen and completion behavior.

Backend / API

  • If the inspection payload does not already expose job type (Spectora vs Attik), the backend may need to expose it (e.g. via existing report/inspection fields or a new flag). Scope is limited to what the mobile app needs to implement the indicator and completion gating; no broader backend changes unless required for that.

Out of scope

  • Web work order UI (e.g. WorkorderActionsDropdown and Spectora links) is unchanged; this work is mobile-only for the inspector app.

References

  • Inspection detail screen: app/(app)/inspection/[id].tsx
  • Inspection data hook: hooks/useInspectionDetails.ts

Please authenticate to join the conversation.

Upvoters
Status

Completed

Board
๐Ÿ 

Main App

Date

2 months ago

Author

Linear

Subscribe to post

Get notified by email when there are changes.