Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 38 ยท Getting Started

Power Apps Studio and the Maker Portal

Take a guided tour of the Power Apps maker portal and Studio: Tree view, Insert pane, properties, formula bar, App checker, Monitor and preview mode.

You create apps in two places. The maker portal (make.powerapps.com) is your home base: it lists apps, tables, flows, solutions and connections. Power Apps Studio is the editor that opens when you create or edit a canvas app. Knowing where everything is makes the rest of the course much easier.

Menu names can shift slightly as Microsoft updates the product, so this lesson describes the stable ideas and the usual places to find them.

The maker portal

After signing in, you see a left navigation with entries such as:

  • Home: shortcuts to create an app and learning resources.
  • Create: start from a blank canvas, from data, from a template, from a design (image) or by describing the app to Copilot.
  • Apps: apps you own or were shared with.
  • Tables: Dataverse tables in the current environment.
  • Flows, Solutions, Connections and more under More or the pinned list.

The environment picker at the top right decides where you are working. Always check it before you create something.

Opening Studio

Choose Create, then Blank app, then Blank canvas app. You name the app and pick a format: Tablet (landscape, more space) or Phone (portrait). The format sets the default screen size, but you can change it later in Settings, Display.

The parts of Studio

Parts of Studio

Tree view Screens and controls
Insert pane Add controls
Formula bar Write Power Fx
Properties pane Tune the selection

Left, top and right of the editor

1 / 2
  • Tree view (left): lists every screen and control as a hierarchy. You select, rename, reorder and hide controls here. Rename early; Button1 tells nobody anything.
  • Insert pane: a catalog of controls and charts, plus your data sources and components.
  • Canvas (center): the design surface where you place and resize controls.
  • Properties pane (right): the common settings for the selected item.
  • Property dropdown and formula bar (top): choose any property of the selected control, such as Text, Fill or OnSelect, and edit its Power Fx formula. This is the most important tool in Studio.
  • Command bar: Undo, Redo, Preview, App checker, Save and Publish.
  • Settings: general options (app name, icon, display, upcoming features).

Properties and the formula bar

Every control has dozens of properties. They fall into groups:

  • Data: Text, Items, Default, Value.
  • Appearance: Fill, Color, Font, Size, BorderColor.
  • Layout: X, Y, Width, Height, Visible.
  • Behavior: OnSelect, OnChange, DisplayMode.

The next stand-in prints a control the way the property list looks, and shows that a property can hold a formula instead of a fixed value.

JS Stand-in: a control as a bag of properties

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Preview, play and publish

  • Press F5 or the Play button to run the app inside Studio. This is the quickest way to test. You can also hold Alt and click controls in the editor to trigger their OnSelect.
  • Save stores a draft version in the cloud. Publish makes the saved version the one end users get. Saving does not publish.
  • Version history (under the app's details page) lets you restore older versions.
  • You can share an app with people or groups, and give co-owner rights to collaborators.

Finding problems

  • App checker lists formula errors, accessibility hints and performance warnings. A red icon in the Tree view marks a control with a formula error.
  • Monitor opens a live trace of events: network calls, formula results and timings. It is the debugging console for Power Apps. Use it to see which data call is slow.
  • Formula error messages appear under the formula bar. Read them; they are usually specific.

The stand-in below mimics an app checker that scans names and flags generic ones, a good habit to enforce.

JS Stand-in: a naming checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Habits worth building now

  1. Name every control with a prefix: lblTitle, btnSave, galOrders, txtSearch.
  2. Set the app name and icon in Settings.
  3. Save often and write a short version note when you publish.
  4. Use App checker and Monitor before sharing.
  5. Keep keyboard shortcuts in mind: Ctrl+Z undo, F5 play, Ctrl+S save.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where do you write Power Fx for a control's property?

    Pick the property from the dropdown, then edit its formula in the formula bar.
  2. 2. What is the difference between Save and Publish?

    Users only see published versions.
  3. 3. Which tool shows a live trace of network calls and formula events?

    Monitor traces events and timings, useful for debugging and performance.
  4. 4. Why rename controls such as Button1?

    Meaningful names help you and your team understand formulas.

Summary

  • The maker portal manages apps, tables, flows and environments; Studio edits canvas apps.
  • Key Studio areas: Tree view, Insert pane, canvas, Properties pane, formula bar.
  • App checker finds errors, Monitor traces events, Play tests, Publish releases.
  • Rename controls and save often.

Next: Build your first canvas app