TecnoStack
Start a projectالعربية

Silent video with on-screen text. The transcript below repeats every screen and describes what it shows.

  1. 0:00–0:06

    Start with the delivered app • Bring the agreement and release history. • Booking A · Illustrative • Agreement • Booking A • Cannot confirm • Illustrative • Coverage to review

    Booking A is an illustrative booking whose confirmation fails. Its record moves below the Agreement heading; Coverage to review stays unresolved. The title and support ask for the delivered app, agreement and release history. The example does not establish included maintenance or change existing defect and compatibility terms.

  2. 0:06–0:12

    Separate work from provider bills • Request the same written breakdown. • Booking A · Illustrative • Work owner • Account owner • Engineering • Provider bills

    The maintenance breakdown has separate Work owner and Account owner destinations. Engineering and Provider bills move in independent lanes into their own destinations. Their separation concerns responsibility and budgeting, with no price, total or included allowance.

  3. 0:12–0:18

    A reply is not a recovery time • Name the owner and coverage hours. • Booking A · Illustrative • Incident owner • Acknowledgement • Booking A • Ticket received • ≠ • Recovery • Retest evidence

    The same Booking A reaches the Incident owner. The receipt state changes to Acknowledgement and Ticket received after arrival. A not-equal sign separates that receipt from Recovery and the unfilled Retest evidence requirement. No recovery deadline or completed repair is demonstrated.

  4. 0:18–0:24

    Retest the affected journey • Check the agreed devices and languages. • Booking A · Illustrative • Proposed retest • Booking A • Agreed devices • Arabic + English

    Booking A enters Proposed retest. Separate open review records identify Agreed devices and Arabic + English as requirements for the affected journey. Highlighting requests attention to those requirements; there is no executed test, success mark or recovered booking result.

  5. 0:24–0:30

    Review before the next release • Keep open work and extra costs visible. • Booking A · Illustrative • Release owner • Decision pending • Evidence request • Open work • Extra-cost approval • Store review, if needed

    Evidence request and Open work take turns entering the body below Release owner. The artwork says Decision pending throughout; the first request clears to make the second intake readable, not to indicate that it was completed. A separate footer names Extra-cost approval, then Store review, if needed. This is a proposed release review, with open work and costs retained and no automatic external approval.

A silent illustrative guide to support responsibilities, separate budget lines, incident ownership and release evidence.

Read the article: App Maintenance Cost Saudi Arabia: Budget and Scope