2 unstable releases

0.4.0 Sep 20, 2023
0.3.0 Oct 20, 2022

#57 in Procedural macros

Download history 71/week @ 2023-12-17 74/week @ 2023-12-24 20/week @ 2023-12-31 70/week @ 2024-01-07 75/week @ 2024-01-14 58/week @ 2024-01-21 30/week @ 2024-01-28 52/week @ 2024-02-04 53/week @ 2024-02-11 68/week @ 2024-02-18 96/week @ 2024-02-25 68/week @ 2024-03-03 79/week @ 2024-03-10 81/week @ 2024-03-17 130/week @ 2024-03-24 171/week @ 2024-03-31

481 downloads per month
Used in 27 crates (5 directly)


730 lines


Rik Arends: @rikarends on twitter, https://fosstodon.org/@rikarends#

Eddy Bruel: @ejpbruel on twitter

Sebastian Michailidis: @SebMichailidis on twitter

Our discord channel for Makepad: https://discord.gg/adqBRq7Ece

Most recent talk about makepad: https://www.youtube.com/watch?v=rC4FCS-oMpg



This is the repository for Makepad, a new way to build UIs in Rust for both native and the web.

Makepad consists of Makepad Framework and Makepad Studio.

Makepad Framework is our UI framework. It consists of multiple crates, but the top level crate is makepad-widgets. For a further explanation of Makepad Framework, please see the README for that crate.

Makepad Studio is a prototype of an IDE that we've built using Makepad Framework. It's still under heavy development, but our eventual goal with Makepad Studio is to create an IDE that enables the design of an application to be changed at runtime. The main crate for Makepad Studio is makepad-studio. Please see the README for that crate for more.

Demo links:





To build the Makepad crates you first need to install Rust. https://www.rust-lang.org/tools/install

Our native builds work on the stable Rust toolchain. However, some of the errors generated by Makepad at runtime (particulary those originating in our DSL) do not contain line information unless you use the nightly Rust toolchain. Moreover, our web builds only work on nightly for now. For this reason, we recommend that you build Makepad using the nightly Rust toolchain.

For the non standard build targets (ios, android, wasm) we have a buildtool called 'cargo-makepad' that you need to install.

Install it from the repo:

cargo install --path=./tools/cargo_makepad

Or install it from cargo (might be behind the repo)

cargo install cargo-makepad

Now this tool can be used to install toolchains per platform needed

cargo makepad wasm install-toolchain

cargo makepad apple ios install-toolchain

cargo makepad android --abi=all install-toolchain

Running makepad studio

Makepad studio allows you to easily build and view the examples, and it uses cargo-makepad internally so be sure to install cargo-makepad as shown above.

cargo run -p makepad-studio --release

Or install it from cargo (might be behind the repo)

cargo install makepad-studio

If you build the wasm applications, you can open it on:

cargo run -p makepad-studio --release

Build & Run Commands

Makepad is a cross-platform UI framework written in Rust. It is in active development, but is already usable to build quick prototypes and simple (or even complicated UI) applications.

One of the key features of the Makepad is its ability to simply, and quickly, build and run applications on multiple platforms, including MacOS, Windows, Linux, Android, iOS, and WebAssembly.

Here are the current/latest instructions on how to build and run Makepad applications on the different platforms.


We will assume the following: Name of application: makepad-example-simple

It can be changed to any one of the existing example apps in the Makepad examples folder.

Build & Run Instructions

Follow step 1 commands below for initial setup of the Makepad build and run environment. After step 2, you may choose any one or more of the platforms you're interested in building for.

1. Setup Makepad

Replace projects with your own directory name.

cd ~/projects

Clone the Makepad repository

git clone https://github.com/makepad/makepad.git


git clone git@github.com:makepad/makepad.git

Change to latest 'rik' branch (Optional)

cd ~/projects/makepad
git branch rik

Install makepad subcommand for cargo

cd ~/projects/makepad
cargo install --path ./tools/cargo_makepad

Install platform toolchains

rustup toolchain install nightly

2. Go To Examples folder (Optional)

cd ~/projects/makepad/examples
ls -l

All examples in this directory have the application name of makepad-example- prefix plus the name of directory.

3. MacOS / PC

Running on Desktop is the quickest way to try out an example app.

cd ~/projects/makepad/examples/simple
cargo run


cd ~/projects/makepad
cargo run -p makepad-example-simple

And there should be a desktop application window now running (may need to click on the icon on MacOS's Dock to show it)

4. Android Build

Install Android toolchain (First time)

cargo makepad android install-toolchain

Install app on Android device or Android emulator

Open either the Android emulator or connect to a real Android device use adb command to make sure there's a single device connected properly, then install and run as below:

cd ~/projects/makepad
cargo makepad android run -p makepad-example-simple --release

The application will be installed and launch on either the emulator or device.

5. iOS Setup & Install

Install IOS toolchain (First time)

xcode-select --install
cargo makepad apple ios install-toolchain

Install app on Apple devivce or iOS simulator

iOS Setup

For iOS, the process is slightly more complicated. The steps involved are:

  1. Enable your iPhone's Developer Mode, please see instructions here: Enable Developer Mode
  2. Setup an Apple Developer account
  3. Setup an empty skeleton project in XCode
    1. File -> New -> Project to create a new "App"
    2. Set the Product Name as makepad-example-simple (used in --app later)
    3. Set the Organization Identifier to a value of your choice, for this example we will use my.test (used in --org later)
    4. Setup the Project Signing & Capabilities to select the proper team account
  4. In XCode, Build/Run this project to install and run the app on the simulator and device
  5. Once the simulator and device has the "skeleton" app installed and running properly, then it is ready for Makepad to install its application.

Makepad Install

We will run the cargo makepad apple ios command, similar to Android build above, but there are some 2 to 4 additional parameters that need to be filled in:


First few parts of the organization identifier (which makes up the Bundle Identifier). Usually in the form of com.somecompany or org.orgname, etc. This is the same value used to setup the initial skeleton app above. For this example:



The name of the application or the project. This is the same as the Product Name used to setup the initial skeleton app above. In this case:


--org-id (real-device only)

Find the <key>ApplicationIdentifierPrefix</key> and use the value in the <string>ORGIDVALUE</string>, from the newest **.mobileprovision file located in the ~/Library/MobileDevice/Provisioning Profiles directory. ORGIDVALUE should be a 10 digit alpha-numeric value.

--ios-version (Optional)

Defaults to 17. Set it to 16 or other values if the device is not running iOS 17.


For this example, we have the Bundle Identifier of my.test.makepad-example-simple

Install app on IOS simulator

cd ~/projects/makepad
cargo makepad apple ios --org=my.test --app=makepad-example-simple run-sim -p makepad-example-simple --release

Install app on IOS device

cd ~/projects/makepad
cargo makepad apple ios --org-id=ORGIDVALUE --org=my.test --app=makepad-example-simple run-device -p makepad-example-simple --release

The application will be installed and launched on either the emulator or real device.

6. WASM Build

To Be Updated

Makepad Commands Quick Reference

Cargo Tools Installations

These are commands that need to be run at least once initially to setup Makepad development environments. They should also be run once in a while or when there are updates to the cargo_makepad script.

rustup update
rustup install nightly
rustup toolchain install nightly

cd ~/projects/makepad
cargo install --path ./tools/cargo_makepad
cargo makepad android toolchain-install
cargo makepad apple ios toolchain-install


Command for installing the app onto an IOS Simulator.

cargo makepad android run -p makepad-example-simple --release

cargo makepad android run -p makepad-example-fractal-zoom --release

cargo makepad android run -p makepad-example-ironfish --release

cargo makepad android run -p makepad-example-news-feed --release

IOS Simulator

Command for installing the app onto an IOS Simulator.

cargo makepad apple ios --org=my.test --app=makepad-example-simple run-sim -p makepad-example-simple --release

cargo makepad apple ios --org=my.test --app=makepad-example-fractal-zoom run-sim -p makepad-example-fractal-zoom --release

cargo makepad apple ios --org=my.test --app=makepad-example-ironfish run-sim -p makepad-example-ironfish --release

cargo makepad apple ios --org=my.test --app=makepad-example-news-feed run-sim -p makepad-example-news-feed --release

IOS Device

Command for installing the app onto a physical IOS device:

cargo makepad apple ios --org-id=ORGIDVALUE --org=my.test --app=makepad-example-simple run-device -p makepad-example-simple --release

cargo makepad apple ios --org-id=ORGIDVALUE --org=my.test --app=makepad-example-fractal-zoom run-device -p makepad-example-fractal-zoom --release

cargo makepad apple ios --org-id=ORGIDVALUE --org=my.test --app=makepad-example-ironfish run-device -p makepad-example-ironfish --release

cargo makepad apple ios --org-id=ORGIDVALUE --org=my.test --app=makepad-example-news-feed run-device -p makepad-example-news-feed --release

Cargo Check Builds

Command to check that the compilation passes for all Makepad supported platforms: (Will use 100% CPU and cause hang machine, only try on high-end systems)

cargo makepad check install-toolchain
cargo makepad check all

No runtime deps