Create an app
Turn a user task into a working app increment, then choose Canvas, model-driven, code app, or generative page.
Start with the outcome you need. Each coached journey helps you choose an experience, build a useful increment, and prepare it for review.
Choose the closest outcome now. Technology choices appear inside the journey, after you have defined the first useful result.
Turn a user task into a working app increment, then choose Canvas, model-driven, code app, or generative page.
Make a repeatable process run reliably with a cloud flow or desktop flow and an observable failure path.
Add a focused agent, mobile experience or extension, and connect it safely to the data and actions it needs.
Package a working increment, validate it, and move it through controlled environments with a recovery plan.
These cards combine local implementation guidance with verified published skills. Each primary action identifies whether it opens a coached journey, hands-on lab, or authoritative skill page.
Build canvas, model-driven, and code apps with intentional navigation, data access, and experience design.
Create a responsive app shell with navigation, state, data access, and error handling.
Bring a user flow and data source. Leave with a working app foundation.
Assemble a role-focused application using Dataverse forms, views, commands, and processes.
Bring a data model and personas. Leave with a navigable model-driven app.
Create the visual system before building a code app so its experience reflects the intended brand rather than template defaults.
Use before implementation. Bring brand assets, audience needs, and experience goals. Receive reusable design tokens and implementation guidance.
Build an event-driven flow with clear scopes, retries, exception paths, and ownership.
Bring the trigger and actions. Leave with a tested cloud flow and runbook notes.
Implement approvals with delegation, escalation, audit history, and cancellation handling.
Bring approval and escalation rules. Leave with a working flow and test scenarios.
Create a grounded custom agent with instructions, knowledge, actions, fallback, and evaluation.
Bring the purpose and knowledge sources. Leave with a testable agent baseline.
Implement tables, relationships, choices, ownership, validation, and seed data.
Bring the approved data blueprint. Leave with a configured schema in a solution.
Expose an external service through a custom connector with authentication, actions, and tests.
Bring an API contract. Leave with a packaged and tested custom connector.
Author or troubleshoot OData and FetchXML queries while avoiding logical-name, lookup-annotation, header, and paging mistakes.
Use for Dataverse/API work. Bring the intent, table metadata, target client, and any failing request. Receive a target-ready query plus handling guidance.
Organize components with publishers, dependencies, environment variables, and references.
Bring the component inventory. Leave with a deployment-ready solution structure.
Configure deployment with source control, validation, approvals, and environment settings.
Bring environment and release decisions. Leave with a working pipeline and checklist.
Provision a teammate's developer environment with repeatable governance defaults instead of manual admin-center setup.
Use before governed development starts. Bring the teammate identity and approved environment settings. Receive a configured developer environment.
Generate feature-presence checks and static security analysis before a Power Apps Code App release.
Use once the code app has testable features. Bring the project and optional requirements. Receive an executable eval suite and HTML dashboard.
Generate presence checks, unit tests, and static security analysis before releasing a Generative Page.
Use once the page has testable features. Bring the component and optional requirements. Receive an executable three-layer eval suite and HTML dashboard.
Use application lifecycle management (ALM) to move changes from development through test to production with versioned solutions, validation, and controlled deployment.
Use Review's self-service guidance and tools to check architecture, security, performance, and solution quality before release.