Building Mobile Applications That Work Efficiently Without an Internet Connection

Build a working method for offline-capable mobile applications that stands up to scrutiny and survives daily pressure.

📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

The documentation for offline-capable mobile applications is accurate only until the next release. Most outages involving the wider technology and systems delivery agenda are triggered by a change somebody considered routine. A common pattern is strong design of the technology and systems delivery discipline paired with weak follow-through. The method assumes participants will be challenged on their handling of offline-capable mobile applications and prepares them for it. The course sets out a working method for the practice within technology and systems delivery that participants can apply the week they return. Participants gain a realistic view of what the technology and systems delivery capability costs and what it returns. The level assumes working familiarity with the technical platform but no prior formal training in offline-capable mobile applications. Organisations that document this area of technology and systems delivery properly resolve disputes about it far more quickly. Participants leave with a first-ninety-days plan for this strand of technology and systems delivery rather than a set of notes.

Expected Learning Outcomes

01

Build a register of the risks attaching to offline-capable mobile applications and keep it current.

02

Assess the current state of offline-capable mobile applications against a structured set of criteria rather than impressions.

03

Build incident response for offline-capable mobile applications with defined severity and escalation.

04

Agree the first three actions on offline-capable mobile applications that will be taken on returning to work.

05

Plan capacity for offline-capable mobile applications against measured growth rather than optimism.

06

Define the availability, performance and recovery targets for offline-capable mobile applications.

07

Structure the service desk and support model for offline-capable mobile applications.

Who Should Attend

01

Service desk and support leads handling incidents in offline-capable mobile applications.

02

Risk managers assessing the exposure created by offline-capable mobile applications.

03

Quality and test engineers verifying offline-capable mobile applications.

04

Anyone whose accountability for offline-capable mobile applications exceeds their current formal training in it.

05

Project managers delivering changes to offline-capable mobile applications.

06

Database administrators managing data within offline-capable mobile applications.

Course Modules

01

Offline-capable mobile applications: architecture and designing for failure

2 sessions · 8 points

Session 1Monitoring offline-capable mobile applications from the user's point of view

  • Review logging on offline-capable mobile applications for coverage and retention.
  • Set delivery and reliability indicators for offline-capable mobile applications the team trusts.
  • Prepare the summary of offline-capable mobile applications that senior management will read.
  • Define incident severity levels for offline-capable mobile applications and the response each triggers.

Session 2Making releases of offline-capable mobile applications routine instead of risky

  • Confirm the support model and escalation path for offline-capable mobile applications.
  • Build the internal briefing that explains offline-capable mobile applications to those affected.
  • Measure current load on offline-capable mobile applications and project it forward twelve months.
  • State the availability and recovery objectives for offline-capable mobile applications as numbers.
02

Offline-capable mobile applications: incident response and severity

2 sessions · 8 points

Session 1Escalation and decision rights in offline-capable mobile applications

  • Establish what evidence demonstrates offline-capable mobile applications is under control.
  • Inventory third-party dependencies inside offline-capable mobile applications and their update status.
  • Confirm that those complying with offline-capable mobile applications understand why it exists.
  • Document the runbook for offline-capable mobile applications to the level a new engineer could use.

Session 2Who answers for offline-capable mobile applications, and to whom

  • Confirm that reporting on offline-capable mobile applications reaches the people who can act.
  • Record the technical debt in offline-capable mobile applications and schedule repayment.
  • Test the failover for offline-capable mobile applications rather than assuming it works.
  • Rank the weaknesses in offline-capable mobile applications by consequence rather than by ease of fixing.
03

Offline-capable mobile applications: security, identity and least privilege

2 sessions · 8 points

Session 1Designing offline-capable mobile applications around how it will fail

  • Map the handovers in offline-capable mobile applications between functions and secure them.
  • Distinguish symptoms from causes when offline-capable mobile applications underperforms.
  • Review access rights on offline-capable mobile applications and remove what is no longer needed.
  • Assess the exit route from any cloud or vendor dependency in offline-capable mobile applications.

Session 2Making offline-capable mobile applications work when resources are constrained

  • Restore a backup of offline-capable mobile applications in a test environment and time it.
  • Arrange the handover of offline-capable mobile applications so capability survives staff changes.
  • Agree what will be standardised in offline-capable mobile applications and what will not.
  • Confirm every release of offline-capable mobile applications can be rolled back within a defined time.
04

Offline-capable mobile applications: capacity, performance and load

2 sessions · 8 points

Session 1Running an incident on offline-capable mobile applications calmly

  • Run a load test on offline-capable mobile applications at expected peak plus a margin.
  • Identify the single points of failure in offline-capable mobile applications.
  • Verify six months later that changes to offline-capable mobile applications have held.
  • Rehearse the briefing on offline-capable mobile applications that would follow an incident.

Session 2Least privilege in offline-capable mobile applications without blocking the work

  • Reduce the variation in how offline-capable mobile applications is carried out between teams.
  • Agree the indicators that will show whether offline-capable mobile applications is improving.
  • Set the review interval for offline-capable mobile applications and who attends.
  • Build the competence framework that supports offline-capable mobile applications.

Choose the package that suits you

Silver Package

At least 3 people

USD1,250
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Gold Package

At least 3 people

USD1,850
  • 5-night stay in a 5-star hotel
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Complete your registration

We will contact you within one business day to confirm.