AdminConsole
Mappls Developer Academy

Learn by shipping the whole journey.

Choose a real industry outcome, your exact runtime, and where you are starting. The Academy assembles a progressive path through source evidence, quickstarts, code labs, hostile stateful scenarios, a tested downloadable capstone, and production acceptance.

Build my curriculum Browse all 39 tutorials
624exact curricula
16industry outcomes
13platforms
39deep tutorials
20tested capstones
Personalized syllabus

Start at your level. Finish at production truth.

Every selection is deterministic and shareable. The planner accepts no credential, location, payload, prompt, evidence file, or arbitrary URL.

Logistics · Web · beginner

Logistics Web developer path

Enter as a beginner developer and finish with a tested, source-grounded a delivery promise customers can trust capstone and an explicit production evidence boundary.

Share this pathOpen curriculum JSON
Modules
7
Guided effort
20–26 hours
State model
hybrid
Capstone tests
17
Loading device-local learning progress…
Your curriculum

Evidence at every level

Fewer failed deliveries and a live, explainable ETA from checkout to doorstep.

Module 01

Understand Logistics location architecture

Beginner

Connect the business outcome, actors, platform lifecycle, product boundaries, and evidence classes before installing a package.

orientationA delivery promise customers can trust5 personas · 5 workflow stagesorientationWeb implementation playbook4 first-success stages · 4 production checksorientationWhy Mappls and the trust boundaryFirst-party marketing evidence separated from repository and fixture evidence
Exit evidence
  • Explain which identities and state belong to the application, the provider, and the user device.
  • Record the exact product, platform, source, entitlement, region, and credential-owner questions that remain open.
Module 02

Prove the Web runtime boundary

Beginner

Reach one observable first success without moving a server credential into an untrusted runtime or treating a fixture as entitlement proof.

quickstartRender one accessible web map15 minutes · public-sourcequickstartYour first trusted Mappls request15 minutes · public-sourcetutorialTurn a device fix into a trustworthy check-in30 min · A privacy-aware check-in that retains both raw evidence and human-readable context.tutorialBuild address autocomplete that users trust20 min · An accessible, resilient delivery-address field.
Exit evidence
  • Capture source identity, configuration generation, a successful proof, and one expected failure signal.
  • Demonstrate cleanup and explain where the credential is owned.
Module 03

Practice contracts, errors, and provenance

Intermediate

Exercise normalized inputs and outputs, generated clients, validation, authentication failure, quota failure, timeout behavior, and source provenance.

contract labGET AutoSuggest APIlegacy-source · stateless · eight generated languagescontract labGET Routing APIlegacy-source · stateless · eight generated languagescontract labGET Gets the details of a single triplegacy-source · stateful · eight generated languagestutorialCall Mappls safely from a trusted server35 min · A credential-safe live server boundary with typed errors, timeout, retry, and provider provenance.tutorialRank responders with a distance matrix45 min · An explainable ETA-based dispatch shortlist rather than a straight-line guess.contract labCredential-free API SandboxSix deterministic scenarios across every normalized operationcontract labErrors and diagnosticsRetry, reconcile-first, and minimized support-evidence decisions
Exit evidence
  • Pass success, empty, invalid-input, denied, rate-limited, and unavailable scenarios.
  • Retain provider identity and source provenance while keeping secrets and payloads out of logs.
Module 04

Compose the 4-product solution

Intermediate

Join stateless and durable lanes without coupling user experience, provider resources, or application aggregates to one request.

orientationA delivery promise customers can trust on Web4 products · 71 contracts · 11 durable journeystutorialCall Mappls safely from a trusted server35 min · A credential-safe live server boundary with typed errors, timeout, retry, and provider provenance.tutorialRank responders with a distance matrix45 min · An explainable ETA-based dispatch shortlist rather than a straight-line guess.tutorialQualify an iOS Mappls release2 hr · A clean-device iOS qualification record spanning SDK, widget, tracking, and distribution boundaries.
Exit evidence
  • Draw the trusted-server, client, provider, and durable-data boundaries.
  • Define stable business, Mappls Pin, provider-resource, request, and aggregate-version identities separately.
Module 05

Attack every durable journey

Advanced

Prove success, replay, optimistic concurrency, invalid-transition safety, unknown-outcome reconciliation, and immutable event causation.

tutorialQualify an iOS Mappls release2 hr · A clean-device iOS qualification record spanning SDK, widget, tracking, and distribution boundaries.tutorialQualify React Native native parity100 min · One JavaScript contract backed by independently qualified Android and iOS behavior.journey labConnected fleet trip6 states · 7 transitions · five fixture scenariosjourney labFleet geofence exception6 states · 5 transitions · five fixture scenariosjourney labCoordinated incident response7 states · 8 transitions · five fixture scenariosjourney labStateful Journey Lab5 hostile-path scenarios · no provider calls or writes
Exit evidence
  • Replay the same command without a second transition or event.
  • Reject stale and invalid commands without mutation, then reconcile an unknown outcome by stable identity.
Module 06

Ship the Care Transfer Desk capstone

Advanced

Use the maintained advanced application as a runnable evidence base, then adapt it to the logistics outcome without weakening its trust boundary.

sample appCare Transfer Desk17 declared tests · Request → confirm facility → assign → custody → review exceptions → acceptsample appDownload Care Transfer DeskComplete checksummed mini-application artifact
Exit evidence
  • Run the sample tests and identify every fixture, provider-adapter, persistence, and failure boundary.
  • Complete the scenario from entry to terminal outcome, including cancellation, restart, and recovery where state is durable.
Module 07

Assemble production acceptance evidence

Advanced

Turn the capstone into a reviewable release without representing repository, generated, or fixture evidence as live Mappls approval.

release controlEnvironment and deployment readinessIsolated development, staging, and production controlsrelease controlAuthentication and credential ownershipExact runtime and product credential pathrelease controlDeveloper console launch journeyApplication-scoped entitlement, credential, request, alert, webhook, and owner proofrelease controlTrust and production gatesExternal authority, conformance, privacy, security, observability, and rollback boundary
Exit evidence
  • Attach current entitlement, package/host, auth, quota, region, privacy, security, accessibility, performance, support, and rollback evidence.
  • Obtain independent approval through the company release process; academy completion itself grants no entitlement or certification.