# [Leo Playground Staging Feedback](stage-pg.leo-lang.org/)

##### Ref: stage-pg.leo-lang.org/

## Feedback

### From Mo

#### Onboarding Tutorial

**From perspective of a dev who knows nothing about Leo / ZK:**
- What's a transition function?
- What're inputs? Why are they private by default?
- What're proofs?
- What's snarkOS?

**General:**

Tooltip (10/12) -> How do you execute zk proofs on-chain with Aleo?
Suggestion: Add link to documentation on generating on-chain proofs.

What assumptions are we making about the users of Leo playground? What background / experience are we expecting they have before coming to this tool? Have they read a documentation page that links them here? Are they pointed here form the landing page site?
Suggestions: Define the target audience for Leo playground. Work on Customer personas and segmentaion. This will help us create journeys for personas with varying experience levels.

#### Deploy modal

How do I find my fee record?
Suggestion: Place a link to a guide for creating an account, using the testnet faucet to get credits, scanning with snarkos to get record, inspecting the json object to find the fee record that must be copied to be used.

What account does the placeholder Private Key point to? Is it supposed to be changed to a newly generated account by the user? If so, where can the use create a new account to use for deploying?

Suggestion:
Create info button to guide the user in creating a new account. Remove placeholder private key. Add a create account / manage accounts feature that enables users to create and manage accounts without having to leave Playground.

What's the peer url field? What are fees? How are they calculated? Why are they necessary? Who recieves fees?

Suggestion:
Create info button so user can learn more about each field and show examples of valid inputs. Link to docs for deeper dive into core Aleo concepts.

**Loved**
- User interface is slick, love the theme and consistency in spacing and typography.
- Onboarding tooltips that educate the user when hoping into Leo playground for the first time.
- Deploy and execute through front-end is a huge win for reducing friction in dev adoption.
- Direct link to Gist is an awesome first step for getting more Leo repos up without the complexity of implementing GitHub OAuth.

#### Bug reports
Bug: Clicking on Resources/Direct link to the Gist results in "internal Server Error"

Expected Output:
Direct link to the gist that can be used to clone project or share on GitHub.

Output:

Bug: Deploying the hello world application results in "Program helloworld.aleo already exists on the network." error

Expected Output:
User can default applications like helloworld and examples to the netowork out of the box.

Output:

Possible solutions:
- Have user enter a unique program ID as first step of Deploy modal. Info button to explain programs must have unique IDs to be dployed. Program ID field should be required and validated.
- Create unique program IDs on page load
- Create unique program IDs on deploy modal load


#### Nit picks
- Estimate fee loading time too long
- Display more info to user on deploy loading screen

---

### From Austin

#### Errors (same as Mo already mentioned)
- The "Direct Link to Gist" errors
- The "Permalink to the Playground" erros
- Same error as the Direct link above
##### Proposed solution
Either remove the "Resources" section and replace it with a single button to report bugs or fix the links.

#### Suggestion

Make the "Designed by Aleo" icon at the bottom clickable to aleo.org.