A two way marketplace for sneakers does not currently exist in Australia that is widely used. There are a few international marketplaces like 'Goat' and 'StockX' that are widely used. These function heavily as a third party that takes a large cut of sales and manages the buying and selling themselves. The closest model that fits the scope of 'KICKSWAP' is 'Depop', which is not focused on shoes and again is an international company. 'KICKSWAP' aims to be the premier marketplace for buying and selling sneakers in a solely Australian focused market. 'KICKSWAP' will operate in a model similar to 'Gumtree', wherein users can be buyers or sellers. These buyers and sellers are then responsible for the management of their sales and purchases with 'KICKSWAP' merely being a platform. The removal of a sales cut also means sellers can save more and pass those savings on to the buyers.

This problem needs solving because both sneaker buyers and sellers need an Australian website that understands the needs and unique ecosystem of shoes within Australia. The large sales cuts that other shoe and clothing marketplaces take from sellers is also an issue. As a majority of people buying and selling sneakers are not those who are doing it professionally, they should not have large amounts of sales profit taken from them.

kickswap.herokuapp.com

github.com/Finbob12/sneaker-buy-sell

The purpose of Kickswap is to create an open platform for Australian sneaker enthusiasts to buy and sell sneakers with each other, without a company taking a large cut of the sales. This will fill a hole in the current market.

Listings: Any user can create a listing on Kickswap for other users to view and purchase. These listings require a brand, style, price, size, picture and description. Any and all of these details can be updated by the user at any point after creating their listing. These listings may also be deleted by the user who created them at any time. If a listing is purchased by a user, the listing is then marked as sold and will no longer show up for other users to view. Buyers and sellers can then organise delivery or pick-up of the listing.

Sitemap:

Home New/Edit Show Sign Up Log In Password Reset Edit Account Conversations Messages Stripe Payment Payment Success 404 Error 500 Error

The target audience for Kickswap is the sneaker community of Australia and anyone else that is looking to buy and/or sell shoes in Australia. This audience will be able to sell their shoes without our site taking a large cut of each sale. Making this a more friendly site to shoe sellers, and hopefully these sellers can pass savings on to the buyers.

Front-end: HTML5, CSS3, SCSS, Embedded Ruby, Bootstrap 4, Javascript.

Back-end: Ruby 2.7.0, Ruby on Rails 6.0.3.

Database: Postgresql.

Deployment: Heroku.

Additional: Stripe, Devise, Ultrahook, AWS S3.

DevOps: Git, Github, VS Code, Balsamiq Wireframes.

• As a visitor with no account, I want to be able to sign up to become a user.
• As a visitor with no account, I want to be able to view all listings.
• As a user, I want to be able to log in to my account.
• As a user, I want to be able to log out out of my account.
• As a user, I want to be able to cancel my account.
• As a user, I want to be able to edit the details of my account I entered when it was created.
• As a user, I want to be able to search for shoes listed on the site.
• As a user, I want to be able to message other users about their listings.
• As a user, I want to be able to see I have a new message without checking my conversations.
• As a user, I do not want other users to see my account page.
• As a user, I do not want other users to see my account details.
• As a user, I do not want other users to be able to edit my listings.
• As a user, I do not want other users to be able to delete my listings.
• As a user, I want to be able to create new listings.
• As a user, I want to be able to edit listings I have created.
• As a user, I want to be able to delete listings I have created.
• As a user, I want to be able to view all listings I have created.
• As a user, I want to be able to purchase listings.
• As a user, I want to be able to sell my listing on the site.
• As a user, I want to be able to have my purchased shoes unlisted so other users don't think they're unsold.

Originally I didn't about the difficulty of having multiple pictures per listings and had the listings less self contained. I also thought it would be possible to have message popups in the corner of the screen.

Again my show had an additional picture in my wireframe and also doesn't have the message user button.

Manage turned into the account page and is missing the edit function here.

Messages is mostly unchanged, each users message is contained in it's own bubble now.

Sign up is mostly the same but a username field was added.

Log in is mostly the same but without the reset password and sign up links.

Payment success is mostly the same but now without the images.

Kickswap is a two sided marketplace built with Ruby on Rails, a framework built with the Ruby programming language. Kickswaps database is handled by Postgresql. A relational database management system that Rails integrates with efficiently. This database is built with various models detailed in the ERD (entity relationship diagram) above. Validation and sanitization are present within each of these models to prevent their manipulation by anything other than allowed parameters given by the Rails app. When a user signs up for an account, their authorization scope is then decided by Devise via logic coded into the app. This authorisation scope then limits the access to creating, editing, deleting and buying listings. As well as the messaging system in the app. Creating listings also uses Amazon S3 to upload and store images in a cloud environment. Listings on the site can be searched and sorted with the Ransack gem. Listings are limited with the will_paginate gem so only 8 listings display per page, reduced SQL queries. Messaging is handled in app by creating database entries that are contained in a conversation table between two users. Stripe handles payment externally through its API, handing off any legality and other related issues to Stripe, simplifying the process. The stripe webhook then handles the state change for sold listings. Logic in the app will the mark the listing as sold and remove it from the viewable listings.

Devise: The Devise gem is used to handle user management within the app. Devise provides inbuilt controller functions and views to assist with sign up, log in and log out. Devise also provides built in helper functions so scope can be built into your application's logic easily. Allowing for many things such as messaging and account page viewing to be limited to their owners, as well as editing and deletion of listings and accounts.

Faker: The Faker gem was used to quickly populate the database with users and listings when the app was initially being built. Faker provides in built methods to use with the seed file to create database entries.

Stripe: The Stripe gem is included to hook up to the Stripe API. This provides a secure and trusted payment method for the application. Having payment handled by a trusted third party removes the need to deal with payment legality.

Ultrahook: Ultrahook was used to provide a locally testable webhook for Stripe.

AWS S3: AWS S3 is used for image uploading and storage for listings in the app. These images are then stored in the cloud, removing the need for in app storage.

Ransack: The Ransack gem is used to provide search and sort functions for the listings on the main page. Ransack has built in methods to provide search and sort in a simple manner.

Will_Paginate: The Will_Paginate gem is used to limit listings displayed per page for the main page. This limitation increasing speed and effeciency in the app by limited SQL queries.

Bootstrap: Bootstrap is a framework used for front end styling. It uses a combination of CSS and Javascript to provide easy styling functions in the embedded Ruby files.

A user has many listings / A listing belongs to a user A user has many messages / A message belongs to a user A user has many conversations / conversations belong to a user A listing has one attached picture / a picture belongs to a listing A conversation has many messages / A message belongs to a conversation

User: The user model has the most relations in the app. When a listing is created it must belong to a user, and a user can create as many listings as they want. A user can also create messages, this will also create a conversation if one does not already. Both messaes and conversation will then belong to the user.

Listing: The listing model has each row created already belonging to a user. The listing also has an attached picture as it is created.

Active Storage: The active storage models exist to transfer data from the database to AWS S3. This relationship is initialised when a listing is created. A picture must be uploaded with a new listing, and belongs to the listing.

Conversation: The conversation model exists only to hold a sender_id and recipient_id to match these against users when a message is initialised. A conversation will always belong to two users, the sender and the recipient. A conversation will also have many messages.

Messages: The message model has each row created belonging to both a user and a conversation.

  create_table "active_storage_attachments", force: :cascade do |t|
    t.string "name", null: false
    t.string "record_type", null: false
    t.bigint "record_id", null: false
    t.bigint "blob_id", null: false
    t.datetime "created_at", null: false
    t.index ["blob_id"], name: "index_active_storage_attachments_on_blob_id"
    t.index ["record_type", "record_id", "name", "blob_id"], name: "index_active_storage_attachments_uniqueness", unique: true
  end

  create_table "active_storage_blobs", force: :cascade do |t|
    t.string "key", null: false
    t.string "filename", null: false
    t.string "content_type"
    t.text "metadata"
    t.bigint "byte_size", null: false
    t.string "checksum", null: false
    t.datetime "created_at", null: false
    t.index ["key"], name: "index_active_storage_blobs_on_key", unique: true
  end

  create_table "conversations", force: :cascade do |t|
    t.integer "sender_id"
    t.integer "recipient_id"
    t.datetime "created_at", precision: 6, null: false
    t.datetime "updated_at", precision: 6, null: false
  end

  create_table "listings", force: :cascade do |t|
    t.string "brand", null: false
    t.string "style", null: false
    t.integer "size", null: false
    t.text "description", null: false
    t.boolean "sold", default: false
    t.datetime "created_at", precision: 6, null: false
    t.datetime "updated_at", precision: 6, null: false
    t.bigint "user_id", null: false
    t.integer "price", null: false
    t.index ["user_id"], name: "index_listings_on_user_id"
  end

  create_table "messages", force: :cascade do |t|
    t.text "body"
    t.bigint "conversation_id"
    t.bigint "user_id"
    t.boolean "read", default: false
    t.datetime "created_at", precision: 6, null: false
    t.datetime "updated_at", precision: 6, null: false
    t.index ["conversation_id"], name: "index_messages_on_conversation_id"
    t.index ["user_id"], name: "index_messages_on_user_id"
  end

  create_table "users", force: :cascade do |t|
    t.string "email", default: "", null: false
    t.string "encrypted_password", default: "", null: false
    t.string "reset_password_token"
    t.datetime "reset_password_sent_at"
    t.datetime "remember_created_at"
    t.datetime "created_at", precision: 6, null: false
    t.datetime "updated_at", precision: 6, null: false
    t.string "username"
    t.index ["email"], name: "index_users_on_email", unique: true
    t.index ["reset_password_token"], name: "index_users_on_reset_password_token", unique: true
    t.index ["username"], name: "index_users_on_username", unique: true
  end

  add_foreign_key "active_storage_attachments", "active_storage_blobs", column: "blob_id"
  add_foreign_key "listings", "users"
end

trello-board

Initial Trello board on November 5th. Due dates were not used for this project due to the lack of chronological necessity in the build. Readme tasks are well defined but app tasks need to be further fleshed out as I approach aspects of the build. Styling tasks to be added as I see necessary.

Basic functionality of the app completed at this point. Starting to find more tasks that need doing and adding to the board.

More tasks have been added as previous tasks were completed. Constantly finding more small tasks that need taking care of at some point. Bugs list added at this point.

Backlog and bugs have filled up more but the project MVP is almost complete. Huge amount of styling also done at this point, but still a lot to go.