Moving from the Motoko Playground to ICP Ninja

Developers Motoko
1

tl;dr: DFINITY is planning to phase out the Motoko Playground Frontend in favor of ICP Ninja as the go-to platform for online canister development. Here’s what it means for you.

What’s Happening

We’re sunsetting the Motoko Playground and making ICP Ninja the primary way to develop and deploy canisters online. Shared projects from Motoko Playground will be migrated to ICP Ninja.

What It Means for Users

  • Shared Projects: If you’ve shared projects on Motoko Playground, they’ll be migrated to ICP Ninja. Old Motoko Playground share links will redirect to ICP Ninja automatically.
  • Sharing new Projects: Sharing new projects from the Motoko Playground will be disabled later next week.
  • Motoko Playground Access: Motoko Playground will display a notice about the switch, and after April 2nd 2025, it’ll stop working and redirect to ICP Ninja.
  • Developers Using Motoko Playground Tools: If you rely on Motoko Playground’s backend or wasm-utils canister for projects, there will be no changes.
    • We ask projects that use the react_app or saved canisters to deploy their own version of these canisters, or use the backend canister directly when possible.
  • New Workflow: Starting today, we recommend using ICP Ninja for all online canister development

Next Steps

We’ll share updates here on the forum to keep you in the loop.

Have feedback? Please let us know below.

6 Likes
2

Seems like the right move but i will note that Motoko Playground is a much better name than ICP Ninja. First ninja is a reference to the user vs ICP Dojo or something.
Second calling someone a ninja is so cringe. At least keep it in motoko/IC theme. If i have to tell people to goto this site to become a IC Ninja… :nauseated_face:
I doubt this is the feedback you’re looking for, but there it is lol
RIP Motoko Playground

1 Like
3

This is an awesome idea and would really streamline development for people that don’t really use the cli. Wow thanks.

1 Like
4

Would this also eliminate the temp 15 minute deploys? Or is that build into ninja as well?

5

Ninja currently has 20 minute temporary deployments. We have ideas about e.g. making the timeout longer for users that are logged in, but nothing concrete yet

1 Like
6

It would be really cool if there’s a way to link to to a canister minted in the nns so an iPad user like myself could deploy directly to a cansiter I control and use Icp.ninja as a full development environment. Idk if that’s technically feasible.

7

Thats a cool idea. For Ninja to deploy code to such a canister, it would also have to be a controller of it. We’re currently looking into ways how to deploy a canister more permanently, we’ll keep you posted once we know what direction we’ll go!

1 Like