Microsoft AI-first Development Weekly: Power Apps Code Apps online mobile support confirmed
Microsoft AI-first Development Weekly covers Power Apps Code Apps, Microsoft Copilot Managed Runtime and Power Platform skills and plugins for AI-first development. These tools help people use AI to build and run business apps.
Power Apps Code Apps: online mobile support confirmed
Microsoft has explicitly confirmed that Power Apps Code Apps are supported online inside the Power Apps mobile app. Code Apps are business web apps written in code and hosted by Power Apps. People can use them in the mobile player while connected to the internet.
This is a support confirmation, rather than a dated launch announcement. Earlier Microsoft guidance said the mobile player was unsupported. Microsoft now says online use is supported, but offline use is not planned in the immediate future. Power Apps for Windows is still listed as unsupported.
Support does not mean every mobile problem is fixed. Users are reporting Android apps stuck while opening and data requests that stop responding. Microsoft is investigating a mobile data-access report; the support reply does not resolve those bugs.
Sources: Microsoft's mobile support confirmation and Android loading report, earlier Microsoft guidance, current documented limitations and mobile data-access issue.
Power Apps: a preview plugin for custom controls
Microsoft has added a Power Apps component framework (PCF) plugin to Power Platform Skills. PCF lets developers create reusable controls, such as a star-rating field or a list of related records, for business apps. The plugin guides an AI coding assistant through planning, creating, testing and deploying those controls. It can also list installed controls and their registered uses.
The plugin is in preview. Its strongest deployment and checking evidence is for model-driven Power Apps, which organise screens around business records. Power Pages support is limited to standard field controls, with guided setup. Canvas apps, whose screens makers arrange themselves, also need guided setup and an administrator's environment setting. Automated checks of the control actually running in a canvas app are not included. No supplied recipe is certified as working at runtime, and mobile and offline behaviour have not been checked.
PCF usage reporting is on by default without a first-run prompt. It sends tool and session details, including organisation identifiers when signed in. A transmission opt-out is available; local diagnostic records remain.
Sources: PCF plugin and privacy controls and capabilities and evidence limits.
Power Apps model-driven apps: safer publishing
The Model Apps plugin now stops a build before writing changes if its working folder belongs to a different Power Platform environment. An environment is a separate place for apps and data, such as testing or production. This check helps prevent changes going to the wrong place.
The Model Apps plugin also checks whether another app uses an AI-generated page through navigation that has been saved but not published. It stops an update to a shared page and names the other app. An upload with an uncertain outcome is not blindly repeated, reducing the risk of duplicate pages or recorded prompts. These are plugin protections, rather than a promise that all publishing conflicts are impossible.
Source: Model Apps changes.
Power Pages: template installation can publish other changes
The Power Pages plugin now follows each template's instructions about publishing the supporting app components it installs. These components can include forms and lists that the website needs. When the template requires publication, the installation workflow makes them available after import.
That publication step can also publish other pending customisations in the same environment. The Power Pages plugin now explains this before asking for approval. It checks the target environment and prepares sample data before starting changes. A failed or timed-out import may leave a partly installed solution, and a timeout does not cancel work already running on the server.
Source: Power Pages template installation changes.
Power Apps Code Apps: easier connections to data
The Power Apps Code Apps command-line tool can now create suitable connections using the person's existing Microsoft sign-in. A connection is the saved permission an app uses to reach another service, such as SharePoint. This can remove a separate browser sign-in step when setting up the app's data sources.
The feature is in version 1.3.0 of the npm command-line tool. It uses single sign-on automatically when that is the connector's only sign-in option. Where a connector offers several options, developers can explicitly choose single sign-on with --use-sso. Unsupported connectors still need their normal sign-in process; this does not bypass permissions or consent.
Source: Power Apps Code Apps command-line package.
Power Apps Code Apps: Microsoft reports an export fix
Microsoft says it has deployed a fix for the Code Apps problem that stopped solution exports. A solution is a package used to move an app and its components between Power Platform environments. The reported failure prevented teams from moving affected Code Apps this way.
Microsoft closed the issue and asked the reporter to try exporting again. The checked conversation does not contain an independent successful retest, so this is a Microsoft-reported fix rather than a confirmed result for every affected app.
Source: Code Apps solution-export fix reply.
Power Apps Code Apps: failed deletions can be detected
The Power Apps Code Apps tool now generates Dataverse delete methods that return the result of the operation. Dataverse stores business records. Previously, an app could ask to delete a record without receiving the result it needed to recognise a refusal, such as a permission failure.
Microsoft says to update the command-line tool to 1.3.0 and refresh the app's data sources to regenerate that code. A user confirmed testing both allowed and refused deletions against a real Dataverse environment. App code must still check the returned result and explain failures to the user.
Source: Dataverse deletion fix and retest.
Power Apps mobile-app plugin: follow edits as they happen
The Power Apps mobile-app plugin now shows a progress page when an AI assistant edits an existing app. It explains the planned changes, shows the build steps and displays screen previews. After successful checks, it offers a scannable code to open the edited app on a device.
The mobile-app plugin also updates the saved app plan to reflect the verified result. An existing app without a plan gets a baseline inferred from what is already there. Clear requests in everyday language can be directed to the matching available skill, without asking the maker to repeat a slash command.
This separate mobile-app building workflow is in private preview and must not be used in production. Its preview phone app is separate from the normal Power Apps mobile player used in the Code Apps support story above.
Sources: Mobile Apps editing workflow and mobile template and preview requirements.
Power Apps model-driven apps: working notes and better form layouts
The Model Apps plugin fixes generated Notes timelines that published successfully but did not appear on the form. A timeline shows notes associated with a business record. A full build can repair the old layout, while preserving a timeline that a maker has resized and reporting controls it cannot safely move.
The Model Apps plugin can also place lists of related records in a chosen tab or column, or between form sections. For example, a project's tasks can sit beside its project details. The generated plan and checks now account for that placement.
Source: Model Apps form changes.
Power Pages: prevent blank Astro pages after upload
The Power Pages plugin adds upload settings for sites built with Astro, a tool for creating websites. Astro can put each page in its own folder. Previously, the upload process could treat those page files as ordinary files, leaving pages other than the landing page blank after deployment.
The new Power Pages settings identify that folder-based layout so the upload tool can put the generated HTML into the site's page content. Validation checks for the setting when the project is clearly an Astro site. Existing configurations keep their previous upload behaviour.
Source: Power Pages Astro upload change.
Copilot Managed Runtime: preview project deployment tools
Copilot Managed Runtime has new command-line tools for deploying the app associated with a managed project and checking its deployment status. Deployment means making a built version available to run. The tools can return a tracking identifier so a developer can check progress later rather than keep the command waiting.
Copilot Managed Runtime also adds support for creating a managed project with an external GitHub repository and selecting named test or production targets in the related deployment workflow. Separate target settings let a developer choose the data connection used for a particular deployment.
These changes are in command-line tool 0.29.0. Copilot Managed Runtime is in public preview. Project commands require the preview projects feature; target configuration requires the separate preview application lifecycle management feature. The service must support the selected route. Project deployment currently handles a single app, rather than every app in a multi-app project. External repositories must meet Microsoft's GitHub Enterprise Cloud requirements.
Sources: Copilot Managed Runtime command-line package and developer requirements.
Copilot Managed Runtime: a skill for saved app records
The Copilot Managed Runtime coding-agent plugin has a new state skill. State means information the app remembers, such as a task's title and whether it is complete. The skill guides the assistant through describing those records, generating code to save and retrieve them, and using that code in the app. A follow-up correction aligns its examples with the generated code and explains filtering and sorting.
This is a new assistant workflow around the existing experimental state tools. The skill checks feature access first and points to other data sources if access is unavailable. Testing data access on a developer's computer requires the supported local gateway setup, which connects local app requests to the runtime's data services. Copilot Managed Runtime remains in public preview; experimental state access and a compatible host are required.
Microsoft's skill describes a built-in record store, but does not identify the underlying database engine. That should not be read as an announcement of a separate database product.
Sources: new state skill, corrected examples and current state workflow and access checks.
Keep up with AI first development with Power Squared on YouTube.
Comments