Round 12 - Call For Bounty Applications - Deadline is May 7

Smart Node UI Wireframes

General Information

What is the nature of the proposed bounty?

Prior to building a UI to use with Smart Node v2’s new HTTP API, we should have someone carefully design the User Experience and Look and Feel.

This bounty would pay for Wireframes that could be used by a future UI developer and graphic designer to create a front-end for Smart Node.

Why are you writing this bounty proposal?

The result of this bounty can be used to direct future bounties to implement the UI.

Benefit

Deleting the grid.

The benefit is that this is the first step to a Smart Node UI.

If the GMC is keen to have one built, this is a good first step that will guide and direct future work.

Which other non-RPL protocols, DAOs, projects, or individuals would stand to benefit from the bounty being successfully completed?

N/A

Work

What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere? What skillsets or knowledge will be required?

Skillsets: Wireframing, UX, Product Design, Node Operation

The ideal contributor is an already-experienced Rocket Pool Node Operator with the above skills.

The wireframe should be a ‘blue sky’ design, and seek to replicate 100% of the functionality of the current CLI, in an organized fashion. Ideally the organization of the UI will be reminiscent of the organization of the CLI commands.

What advice would you give a bounty hunter working on this bounty?

  1. If you have never run smart node before, run a testnet node and thoroughly familiarize yourself with the current user experience
  2. Don’t include auth in the wireframe, it will most likely be handled by external tools.
  3. No web3 integration should be necessary, as the backend has access to the node wallet’s private keys. However, leave the door open to the notion of using one in the future, so a node can be controlled by a hardware wallet via the UI.
  4. Try to separate “read only” from “read/write” in the UI mockup, similar to how some commands currently are read only (eg rocketpool node status) and others are read/write (eg rocketpool minipool stake.
  5. KISS - Keep It Simple… Sally.
  6. Use figma, it’s great at this.

Should the output of this bounty be available under an open source license?

Yes, an open source media license.

Costs

How much do you think the completion of this bounty worth to Rocket Pool (in USD)?

Oh, let’s say $2,000. I want someone to really think critically about the UX and take their time getting it right.

How much work will be needed to verify this bounty has been completed? What skillsets or knowledge will be required?

Verification will be handled by the GMC. The GMC should take care to analyze the UX and ensure the contributor has been thorough.

Structure

How would you structure this bounty, and why?

A single payment on delivery of the wireframes.

Is this bounty repeatable?

No

Are there any reasonable circumstances under which this bounty should be withdrawn? Should it expire?

Expire it after 4 weeks elapse from the date at which it is no longer in the pDAO challenge window. Expiry here being used largely as a deadline.

Conflicts of Interest

Does the person or persons proposing the bounty have any conflicts of interest to disclose? (Please disclose here if you are a member of the GMC or if any member of the GMC would benefit directly financially from the successful completion of the bounty).

No

Will the applicant, or any protocol or project in which the applicant has a vested interest (other than Rocket Pool), benefit financially if the bounty is successfully completed?

No

1 Like