The Givepoint Hub is a project I worked on when I worked at Zomaron. Givepoint was a product consisting of a self-serve, cashless donation kiosk, and an online donation portal. The purpose of the Hub was to create a way for clients to manage the backend of both their kiosk and online donation page. We wanted to offer a dashboard to easily view how their donations were doing, a comprehensive reporting tool that could be exported, and a detailed list of donations and donors.

In our design team, there were 4 of us. We brainstormed ways to have all the pages flow nicely while still being intuitive. We were on a tight deadline, so we figured out how to design all the pages in just a couple different styles, making our jobs a little easier, and also making the pages easy to use for the clients, since each page would function similarly.

We decided to use the sidebar for details all throughout the application. We needed a place for a lot of details, and we figured that this would be the best way to go about that. As the project went a long, we came across issues with the sidebars, and often hd lengthly discussion about the main use for the sidebar, and sidebars vs. modals because of times when things would need to be edited. In the end, we stuck with the sidebar for details, and when something was being created or edited, it would appear in a modal.

The toughest page was definitely the reporting page because it was so different from the rest. It was not just a list of details, it was graphs showing various information that could be changed.

I was the main person working on this page, so I spent a lot of time working with the product manager on ways to make the page work seamlessly but easily. There were three different reporting pages, each one with a different kind of graph and different information. We had to incorporate all the information that a client would want to see while making the customizability easy for anyone to use. All this had to be thought out along with how it would function on a mobile device as well.

The "list" pages were easier than the reporting page, but we still had to incorporate a lot of information that could possibly lead to other pages. For example, a donor's donation could be clicked on, which would lead to the donations page, showing slightly different information.

During this project, the company was at the start of its growth, so there was no product team or UX team. It was simply us designers, working with one product manager, and the executives. We had to do a lot of storyboarding, mapping, and testing on our own, but in the end we learned a lot of about the process, UX, and working as a team.

The home screen would house the consumer's favourite places, show popular places, and have the ability to explore.

The main pages would all be on a bottom navigation for easy navigation.

The hamburger menu would be where a viewer could find the about, changelog, privacy policy, etc.

Filters would be found on the top right corner for easy accessibility when searching.

Places could easily be favourited, simply by pressing on the heart next to a salon's name.

In search mode, viewers would be able to quickly see the services offered, rating, location, and profile picture.

Finally, the "Account" screen would be where a consumer could edit their profile, change their password, logout, or delete their account.

Unfortunately, the app idea never made it any further than the first stage of design, as the person with the original idea for it went on to do other things. Even though the app never became anything, I still enjoyed the process and experience of having to take just a small idea and build everything by myself from there.