ZACK’S POWER
After exploring personas, jobs-to-be-done and testing demand, we focused our prototype on these user stories:
“As a new homeowner, �I want to see what plans I can buy, �so that I can compare them and select the plan that’s right for me.”
Then we looked at UI patterns and prototyped our approach to the user interface.
Then we iteratively coded, tested, and deployed the app using AWS Amplify
For residential and small business electricity customers who want to trim their electric bill, Zack’s Power is a retail electric provider that supplies off-site renewable energy for less than the cost of the most competitively-priced green or brown power alternatives. Unlike currently available options such as on-site solar, our product requires no new installation or maintenance, covers 100% of the customer’s load, and is directly traceable to new renewable energy assets.
Zach’s Power Creates Better Energy Choices for Homeowners
A Web Application for the Residential Energy Market
“As a new homeowner, �I want to know my electricity service options, � so that I can choose the best plan for me.”
The specific content here is the property of the Zack’s Power Project. You are free to use this template to create a personal portfolio entry. For more specifics, see http://www.alexandercowan.com/legal/
Hiya- Welcome to this template.
To zoom in, go to View -> Zoom in the Google Slides menu.
The first thing you'll want to do is create an editable copy for yourself. You can do that by going to File -> Make a copy.
Mac Safari Users: the type looks off, but that goes away once you make a copy.
The instructions on what to do from that point are here: http://www.alexandercowan.com/creating-personal-innovation-portfolio/#ApplicationnbspDesign_Agile_Development
(And, sorry, you’ll need to delete all these messages in the margins.)
Note on Intro Text:
This is a clinical positioning statement. See here for the format: http://bit.ly/pos-stat
I like that format because it touches the major points of a product or project in short form. Feel free, of course, to change the format. It's important to keep it short for this medium (the portfolio entry).
The headline that precedes it is a core statement about the problem/need/job this app deals with.
I actually recommend first writing the position statement.
Note on Activities:
Most of my students have been using the Venture Design process to decide what to build:
http://www.alexandercowan.com/venture-design/
If that's you, this statement may be fine as-is. If not, you may want to change it.
Note on User Stories:
Pick 2-3 key user stories that explain the focal points of your portfolio entry.
For more on user stories:
Note on Screen Shots:
Pick a few screenshots from your prototypes that relate to the functionality you implemented.
For more on prototyping and using Balsamiq:
http://www.alexandercowan.com/build-your-first-prototype-in-30-minutes/
Note on Screen Shots/2:
These are screenshots from the actual app
Note on Legal Footer:
You can remove this for your entry (terms of course still apply)
We considered how to minimize our custom code footprint and simplify our toolchain and ended up with the stack below.
Vanilla HTML �& CSS
Tailwind CSS
Views & �Front Controllers
Firebase SDK
Vanilla JS
Core/Backend Controllers
Google Firebase: Authentication & Firestore
Data Model