README.md

MillionaireMart

Note: this is the end result of a project I completed for Coder Academy back in June 2020. It is essentially a mock marketplace for millionaires to make impulse purchases. Built in Ruby on Rails. The original documentation can be found below.

Deployed link (heroku): https://millionairemart.herokuapp.com/

---

What is the problem MillionaireMart is trying to solve?

Wealth disparity is very real, one man's fortune is another's change. There is a real market for selling interesting but expensive items that otherwise would be hard to purchase or source elsewhere on the internet. This is where MillionaireMart steps in. It is place where those with lots of money can easily spend lots of money, while also encouraging creative products and services to be listed by people looking to make money.

Why is it a problem that needs solving?

Some people have very high disposable income, and not a whole lot to spend it on.

User Stories

• As a user I can create an account, which saves my address and email. I want this information to be kept safe from others.
• As a user I want to be able to login/logout, as well as edit my accounts details.
• As a user without an account, I want to be able to view collections and listings.
• As a user I want to be able to view all listings within collections, or view all without category filtering.
• As a user with an account I want to be able to create collections, and delete or edit those collections which I've created.
• As a user with an account I want to be able to create listings that belong to a collection, that have a price, title and description.
• As a user with an account I want to be able to edit/delete listings that I've created.
• As a user can view listings with collections/categories, or they can see all listings at once.
• As a user with an account I want to be able to purchase listed items in a safe way.
• As a user with an account I want to be able to view all successful orders that I've purchased.

Wireframes and ERD

App Description

Purpose

MillionaireMart is a two-way marketplace, for those with high disposable incomes. It aims to provide a platform for users to buy/sell interesting but rare products and service that to most would seem needlessly expensive. The purpose of this app is twofold: to allow users to create an account by which they can create listings that belong to a collection, or buy other user's listings.

Functionality/features

MillionaireMart has the following features:

• Users can create an account, using the gem devise, which ensures the safe handling of provided user information. This account holds profile information that helps with smooth handling of purchases.
• Profile information can be edited post-creation, as well as deleted.
• Those users with accounts can purchase others listings, or create their own listings to sell. These listings can have: a tile, description, image, and price.
• Users can create collections, that have: a title, description and image. Listings can then be added to these collections.
• These listings and collections have set user scope, so that only those who created the listing/collection can edit or delete them.
• Users can view collections and listings despite not having an account.
• The website handles secure purchasing of items through stripe if an account has been created.
• Users can track completed orders they've made.

Sitemap

Screenshots

Home Collections Page Listing page Collection Page About/Contact Page

Target Audience

The target audience is for those with very high disposable incomes/wealth, that are prone to impulse purchasing interesting and unique products/services.

Tech Stack

The actual app utilises the following stack:

• Ruby 2.7.0, with gems: Devise, Ultrahook, Stripe, and aws-sdk-s3
• Ruby on Rails
• HTML
• CSS/SCSS, and bootstrap
• PostgreSQL
• Javascript
• Amazon S3
• Heroku
• Stripe

These tools were also used to help with creating the app:

• DBeaver
• Balsamiq
• VS Code
• Github
• Trello
• LucidChart

Components

Authentication is done through a gem called Devise. This ensures user data (eg. password) is properly secured (encrypted in the case of passwords) and sanitised.

Rails utilises a framework known as MVC standing for Model View Controller. This means that this application, seperates functioning into these three distinct areas. The first is the Model which deals with any logic associated with the database. It is where relations between tables are defined.
The second is the View whcih deals with how the information is displayed to the user, with each page having its own views.
Finally, we come to the Controller which is the bridge between these twocomponents. The controller is in charge of any logic that is to be done for the app to function correctly.
Routes make all of this possible by directing where information should be sent and handled, it tells the controller how to respond to different requests.

Model/DB Relationships

DB Schema Design

MillionaireMart utilises PostgreSQL for its database management, and has four tables that it employs within this database. These tables are: users; collections; listings; and orders.

The active record associations/relationships between said tables are set up in the following way:

• A user has_many listings, collections, and orders, which arte alldependent: :delete_all meaning they get deleted when users are deleted.
• A listing belongs_to a user and collection. It also has_many orders, which are dependent: :delete_all meaning orders get deleted when listings are deleted.
• A collection belongs_to a user; and has_many listings, which are dependent: :delete_all meaning listings in the categories get deleted when collections are deleted.
• An order belongs_to a user and a listing.

These relations are linked through the use of foreign keys, which reference primary keys from other tables. This directly links the tables, and allows for logic relational logic throughout your app such as User.collections.

Amazon S3 is also utilised to add and store images, where both listing and collection can have one attached image.

Task Management Process

Once I'd figured out the idea I was going with, I set out some basic user stories to determine the basic functionality I wanted the app to have. From here I set up a trello board employing a very basic kanban setup, seperating tasks into to-do, in-progress, completed and potential-task categories. This was checked next to the task requirements to ensure all requirements were met. This setup in progress can be seen in the image below.

From there I set out the model I was going to go with, using the website lucidCharts.com. Then very basic wireframes were designed for both web and mobile views, using the application balsamiq. The outcomes of both these processes have been provided in sections that can be seen above.

Third Party Services

MillionaireMart relies on the following third party services:

• Amazon S3 for cloud-based listing/collection photo storage.
• The gem Devise for user authentication. This gem ensures sesnitive data is protection, whicle also providing inbuilt functions to help make the process of user management easier across the application.
• Stripe and its associated gem for payment handling, which ensures that paymenst are conducted in a safe and secure way.
• Bootstrap is a CSS Framework that helps to make styling a smoother and easier process.
• Heroku for app deployment
• Ultrahook and its associated gem for managing stripe payment success calls
• Faker gem for generating fake data for use in the seed file.