Challenge Summary
Welcome to SunShot - Sun Swarm - Community Solar Wireframe Challenge. This challenge is focused on creating a wireframe for a responsive application that promotes “Community Solar” by allowing people who cannot put solar on their roof can subscribe to eligible solar projects nearby.
About the Project:
The SunSwarm platform is our solution to create a scalable platform that connects interested energy consumers, Utilities and solar developers in each respective jurisdiction to facilitate compliant community solar projects for respective jurisdictions. The core of the platform provides cost effective project management tools for Developer companies and organizations to organize and develop Community Solar Projects by identifying optimal pre-subscribers interested in the project, sites for grid connection generation projects, customer billing tools, online regulatory filings, and administrative regulatory report generation.
At the end of this challenge, we are looking to see intuitive and easy to use "wireframe concepts" that will help us design and build UI/UX in the next phase of this project!
This challenge is focused on "wireframe" output and results.
Be creative in your wireframes!
NOTE: We are awarding $100 for all best submissions at checkpoint!
Round 1
Submit your wireframe for checkpoint review..
1) Landing Page
2) Developer - Home / My Projects
3) Developer - Sign Up / Sign In
4) Developer - Premium Account Upgrade (signed in)
5) Developer - Premium Account Sign Up
6) Create New Project
7) Developer “Edit Project”
8) Developer - Account Settings
Add comments about your wireframe, make sure all pages have correct flow!
Round 2
Final wireframe + any checkpoint feedback implemented!
Any comments about your wireframe, make sure all pages have correct flow!
This application has two types of users (Subscribers and Developers). Subscribers seeking solar submit their contact info and developers submit projects they are working on. SunShot backend connects (matches) a subscriber with developers.
Wireframe Guidelines:
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when you create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details below.
- Screen Sizes: We would like you to focus on Desktop and have the size as 1024px and height as required
Required Pages:
Below are some of the features required in this application, but you are not limited to this, we are open to flows and suggestions on how things could work - so feel free to expand and suggest us what would be best for this type of application!!
1) Landing Page (not signed in):
- This page will show the purpose of the site “Community Solar” description, you can use a copy as “Community solar is….”
- Need a place in this page where we can show “How Sunswarm works…”
- This page need to be more enticing to users and should convey the information effectively.
- Include a navigation in this page, have these links “About, Developers, Subscribers, Signin/Signup, Projects”.
- There are two types of users for this application (Subscribers and Developers) and we need to provide ways for them learn more on what they can do with this site and options to sign up / login.
Subscribers:
- Show a brief description that says “Want to sign up for community solar (1 to 2 sentences - use dummy text) and provide a link to learn more and this will take them to
Subscriber (Home Page) - see below for more details on this page.
- If they are new to the site then they should have the ability to “Sign up”, so show a “Sign Up” button and this will take them to “Subscriber (Sign Up).
Developers:
- Show a brief description that says “Want to develop a Community Solar Project? and provide a link to learn more and this will take them to Developer (Home Page) - see below for more details on this page.
- If they are new to the site then they should have the ability to “Sign up”, so show a “Sign Up” button and this will take them to “Developer" (Sign Up).
About Sun Swarm:
- We need to display a brief description about the company
- You can use this text copy “Sun swarm is a company dedicated to community solar. We are a winner of the DOE Sunshot.”
A. Developers:
2) Developer Home / My Projects:
- User will see a list of “My Projects” in this page.
- Would it be good to provide search and filter options?
- They will need option to edit, delete a project.
- Provide option to create a new project (maybe we need a button like “Add New Project” button that will help them create a new project).
- They will be able to see “A summary of Matched Subscribers that qualify for the developer’s projects”.
- We need a way to indicate/show some kind of banner with a button that says “Learn about upgrading to Premium Account to gain access to Premium tools”
If the user is not signed in, they will see the text that says:
- “Developers can post projects online and sign up new subscribers through our platform…”
- Provide a button to “Sign up now!”
- Once they click on sign up, they will be able to view the new developer home page.
3) Developer - Sign Up / Sign In:
Below can be on a separate page, we would like you to think on what would give the user best user experience.
Developer - Sign Up:
- Developers who are not signed will sign up here
- They will need to enter minimum details (Company Name, Email, Password, Retype Password).
- What other fields will be required in this signup form?
- On successful sign up, what needs to be shown?
Developer - Sign In:
- Developers who already have signed up will be able to sign-in to the application.
- Users will need to provide Email and Password in order to login into the app.
4) Developer - Premium Account Upgrade (signed in):
- This page describes about the benefits of upgrading to a premium account
- You can use the below text (feel free to improve them as required):
“Premium services allow you to see details about customer savings. Here’s what you get…”
- Unsubscribed subscriber heat map (paid)
- Subscriber details (paid)
- Developer tools - site locator, legal agreements, Subscriber savings estimations
- Button - Sign up for Premium”
5) Developer - Premium Account Sign Up:
- Note: A user will be signed-in in this view..this is just an account upgrade!
- This page will get the credit card information, as payment is involved to upgrade their account.
- What other information need to be shown in this page to make it complete?
6) Create New Project:
- Developers will have the ability to create a new project.
- In order to create a new project, they need to enter below details:
- - Project name
- - Business type (non-profit, etc)
- - Address
- - Name of the local Utility
- - Size (kW, kWh/yr)
- - Business model (checkboxes): Pay as you go, Pay upfront
- - Subscriber Period
- - Target Market (non-profit, etc.)
- - Project Start date
- - If project is in CA, checkbox to indicate if Developer wants detailed savings estimation for Subscriber (Premium)
- - Button to submit the new project data.
- What else needs to be shown once the user submits the project data? (looking for your thoughts).
7) Developer “Edit Project”:
- This is same as “Create New Project”, all details are the same except that it will show some more additional details about the subscribers.
- Please include the below details (note: user cannot edit below details)
Project Details (uneditable)
- - Subscribers (subscriber savings)
- - % of KWh subscribed
- - Extra aggregate offtake potential of customers.
8) Developer - Account Settings:
This page will show the account details:
* Account Type: Premium or Free
* Sign up for premium: Need a way to indicate/show some kind of banner with a button that says “Learn about upgrading to Premium Account to gain access to Premium tools”.
* Show the payment information
* Provide options to “Delete account”
B. Subscribers:
9) Subscriber - Home/List of Projects (not signed in):
- Assumption a user is not signed in
- We show list of projects / map and they can browse through the projects and clicking on a project goes to the project details page.
- A subscriber will be able to see many projects but won’t have the ability to subscribe until they are signed in.
- We show this text “These are projects you can subscribe to (Project List/Map). Sign up for an existing project (or) don’t see a project fit, fill out Subscriber form and we’ll let you know when a project comes online that you can subscribe to.”
- Would it be good to provide search and filter options?
- It would be good to show the list of projects on a map, by default we can capture user’s geo-location and show the projects near them or be able to see all projects in the map.
- Looking for your thoughts on how to show the projects.
- Provide a button to sign up for sun swarm.
10) Subscriber - Sign up / Sign In:
New Subscriber - Sign Up:
- Provide option to “Sign up with facebook?”
- They should have the ability to “Sign up with email”
Subscriber details (form):
- Name
- Address
- Email address
- Type (Residential, Commercial, Industrial)
- Average Monthly Electricity Bill - Slider with a text field
- Utility
- Bill Type (optional)
- Affiliation (optional)
New Subscriber - Sign In:
- This is same as developer sign in process.
- Subscribers who already have signed up will be able to sign-in to the application.
- Users will need to provide Email and Password in order to login into the app.
11) Subscriber - Project Details Page:
- Based on whether the user is signed in or not, we need to display appropriate details
Users Not signed in:
- This page will need to show below project details:
- - - project name
- - - business type
- - - location
- - - utility
- - - size (kW)
- - - business model (pay as you go, pay upfront)
- - - Subscriber Period (e.g., 20 years)
- - - Target Market (non-profit, etc.)
- - - Project Start date
- - - Percent subscribed
- - - subscribe button (if not signed in, show sun-swarm sign up screen (or) if signed in, take to Project Subscription View)
User Signed in:
- For users who are signed in, indicate if Subscriber is qualified for project or not. This is based on the matching algorithm.
- If user is already subscribed for project, display “subscribed”
- If user has not already subscribed, show a button to subscribe to a project, they will be taken to project subscription form.
- Show the percent subscribed
- Display the “Savings Estimation”
- - - Potential Electricity savings
- - - Potential $ savings - If user has already submitted bill history info, show savings based on bill history. Otherwise, savings are based on user input form.
- - - GHG (Greenhouse Gas) reduced
12) Subscriber - Project Subscription Form (Signed in):
- Users who have chosen to subscribe to a project will see this project subscription form
- We would like you to show the below text in your wireframes:
“By subscribing you’re just letting the developer know you’re interest in the project, the developer will then reach out to you and let you know the next steps…”
Subscription Summary (NOTE: these fields are not editable):
- Project Name
- Percent Subscribed
- Subscriber Period (e.g., 20 years)
- Savings Estimation
- - - Potential Electricity savings
- - - Potential $ Savings
- - - - - If in CA and developer has indicated that they want bill history info for this project, show bill history Button - perhaps we should show this button somewhere else after the user has subscribed.
- - - - - Otherwise, savings are based on user input form.
- - - GHG (Greenhouse Gas) reduced
- Button - Subscribe to project
- Review Subscription Agreement. Sign using Docusign, and submit to Developer (Docusign API will be used to sign this form)
- Docusign Status: It could one of the following status "Signed, Not Sent, Emailed, but not signed, Resend Docusign"
13) Subscriber - Account Settings (signed in):
- This shows the account settings for the subscriber
- Provide options to “Delete account”
- What other information can be shown in this view.
Additional Pages:
- If you feel there are any other pages that can be added to show the flow, please feel free to do so!
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
Target Audience:
- Developers: Build or even own solar plants
- Subscriber: Someone having/seeking community solar
Judging Criteria:
Your submission will be judged on the following criteria:
- User Experience.
- Completeness and accuracy of the wireframe.
- How well your wireframes provide a consistent user flow.
- Any suggestions, interactions and user flow you recommend (provide any notes or comments for the client).
Submission & Source Files:
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.