Test native mobile applications under realistic load before it meets real load.
Building High-Performance Native Mobile Applications
Build a working method for native mobile applications that stands up to scrutiny and survives daily pressure.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for native mobile applications are commercial commitments, whatever the engineering team calls them. The documentation for the technology and systems delivery capability is accurate only until the next release. Post-incident reviews keep identifying weaknesses in this aspect of technology and systems delivery that were visible long before the incident. Exercises escalate in difficulty, ending with the ambiguous situations that make native mobile applications hard in practice. The programme takes participants through this area of technology and systems delivery end to end, from framing the problem to closing it out. The programme suits teams tackling the technology and systems delivery discipline together as readily as individuals attending alone. The course leaves participants able to diagnose weaknesses in native mobile applications before they become incidents. What blocks progress on this part of technology and systems delivery is usually unclear ownership rather than unclear intent. It ends with a prioritised list of changes to the technology and systems delivery capability that the participant is prepared to defend internally.
Expected Learning Outcomes
Document native mobile applications to the level a new engineer could operate it.
Establish monitoring and alerting on native mobile applications that reflects user experience.
Translate policy on native mobile applications into procedures that hold up under day-to-day pressure.
Build incident response for native mobile applications with defined severity and escalation.
Build a concise technical standard for native mobile applications that colleagues can follow without further explanation.
Assess the current state of native mobile applications against a structured set of criteria rather than impressions.
Who Should Attend
Infrastructure and platform engineers operating native mobile applications.
Training and development staff building internal capability in native mobile applications.
Vendor managers overseeing suppliers involved in native mobile applications.
Quality and test engineers verifying native mobile applications.
Staff seconded into improvement work on native mobile applications.
Network and communications engineers supporting native mobile applications.
Course Modules
Native mobile applications: incident response and severity
2 sessions · 8 pointsSession 1Testing native mobile applications before relying on it
- Check that native mobile applications still works when volumes rise unexpectedly.
- Set delivery and reliability indicators for native mobile applications the team trusts.
- Map the handovers in native mobile applications between functions and secure them.
- Run a load test on native mobile applications at expected peak plus a margin.
Session 2Setting availability and recovery targets for native mobile applications honestly
- Confirm data retention and deletion rules applied within native mobile applications.
- Document the runbook for native mobile applications to the level a new engineer could use.
- Rehearse the briefing on native mobile applications that would follow an incident.
- Identify the single points of failure in native mobile applications.
Native mobile applications: security, identity and least privilege
2 sessions · 8 pointsSession 1Reading the current state of native mobile applications honestly
- Close out actions on native mobile applications rather than leaving them open indefinitely.
- Inventory third-party dependencies inside native mobile applications and their update status.
- Remove steps in native mobile applications that add effort without adding assurance.
- Set the review interval for native mobile applications and who attends.
Session 2Dependencies and supply chain risk in native mobile applications
- Establish what evidence demonstrates native mobile applications is under control.
- Configure alerting on native mobile applications that reflects what users experience.
- Plan the sequence in which improvements to native mobile applications will be introduced.
- Assign responsibility for keeping documentation of native mobile applications current.
Native mobile applications: requirements, targets and service levels
2 sessions · 8 pointsSession 1Moving native mobile applications from approval to execution
- Measure current load on native mobile applications and project it forward twelve months.
- Restore a backup of native mobile applications in a test environment and time it.
- Test the failover for native mobile applications rather than assuming it works.
- Assess the exit route from any cloud or vendor dependency in native mobile applications.
Session 2Designing native mobile applications around how it will fail
- Agree what will be standardised in native mobile applications and what will not.
- Agree the smallest change to native mobile applications that would be visibly useful.
- Record the technical debt in native mobile applications and schedule repayment.
- State the availability and recovery objectives for native mobile applications as numbers.
Native mobile applications: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Documenting native mobile applications so someone else can operate it
- Collect evidence on the present handling of native mobile applications before proposing changes.
- Set out how exceptions to native mobile applications are requested and approved.
- Estimate the resource native mobile applications requires to run as designed.
- Review logging on native mobile applications for coverage and retention.
Session 2Retiring the legacy part of native mobile applications
- Set out the decisions in native mobile applications that require sign-off and by whom.
- Apply change control to native mobile applications including emergency changes.
- Define incident severity levels for native mobile applications and the response each triggers.
- Identify single points of dependency in native mobile applications and reduce them.
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.