Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Mobile Application Developer Source-Aware Guide
Defines source-aware mobile application development, evidence handling, and action boundaries.
Read the fileOverview
Mobile Application Developer overview
Use this bundle to prepare source-aware mobile application development analysis and a review-ready mobile delivery brief.
Read the fileWorkflow
Mobile Application Developer source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: users, requirements, supported OS and device versions, acceptance criteria, and release channels; repository, language.
Read the fileTemplate
mobile delivery brief
Review-ready artifact for mobile application development, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Mobile Application Developer work, plus teams reviewing its decisions and outputs
- Teams working in Software engineering, Mobile products
When to use it
- A Mobile Application Developer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare a mobile delivery brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- mobile delivery brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Mobile Application Developer work by producing mobile delivery brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with openriskmanual.org — Wiki / ISCO Specialization 2514.2.2 Mobile Application Developer, then confirm that the reference is current and applicable. Inspect Mobile Application Developer Source-Aware Guide before drafting.
Context path: bundles/roles/mobile-application-developer
What the bundle includes
Frameworks
- source-evidence matrix
- mobile application development review matrix
- qualified-review gate
Evaluations
- Mobile Application Developer source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the cited official, originator, standards, or professional sources for general mobile application development context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for users, requirements, supported OS and device versions, acceptance criteria, and release channels; repository, language, SDK, framework, dependencies, build tools, signing, and environments; API, storage, permissions, authentication, privacy, security, and offline behavior; UI states, localization, accessibility, performance, battery, network, and device tests; store policies, entitlements, telemetry, release, rollback, and approvals.
- Do not infer device behavior, permission use, compatibility, accessibility, security, test outcome, store acceptance, or production state.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
- Require explicit confirmation before using signing credentials, changing permissions or data handling, uploading builds, releasing apps, or claiming compliance.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.