Release

[rbanos-mv]

XpenseS

XpenseS is a mobile web application where you can manage your budget: you have a list of transactions associated with a category, so that you can see how much money you spent and on what..

Live demo

• Visit: https://glacial-thicket-62528.herokuapp.com/
  • Sign up to create your user and password before you can use the app.

Recorded video

• Click on this link to watch a demo recorded in video.

This PR includes the following requirements:

General requirements

• Make sure that there are no linter errors.
• Make sure that you used correct gitflow.
• Make sure that you documented your work in a professional way.

Ruby requirements

• Follow our list of best practices for Ruby.

Project requirements

Design

• You should follow these design guidelines, including:
  • Colors.
  • Typography: font face, size and weight.
  • Layout: composition and space between elements.

[x] The Creative Commons license of the design requires that you give appropriate credit to the author. Therefore, you must do it in the README of your project.

• Original design idea by Gregoire Vella on Behance.

Interactions

• Splash screen

  • A simple page with the name of your app, and links to the sign up and log in pages.

• Sign up and log in pages

  • The user should be able to register in the app with full name, email and password (all mandatory).
  • The user can log into the app using email and password.
  • If the user is not logged in, they can't access pages that require the user to be logged in (all the pages described below).

• Home page (catagories page)

  • When the user logs in, they are presented with the categories page.
  • For each category, the user can see their name, icon and the total amount of all the transactions that belongs to that category.
  • When the user clicks (or taps) on a category item, the application navigates to the transactions page for that category.
  • There is a button "add a new category" at the bottom that brings the user to the page to create a new category.

• Transactions page

  • For a given category, the list of transactions is presented, ordered by the most recent.
  • At the top of the page the user could see the total amount for the category (sum of all of the amounts of the transactions in that category).
  • There is a button "add a new transaction" at the bottom that brings the user to the page to create a new transaction.
  • When the user clicks on the "Back" button (<), the user navigates to the home page.

• "Add a new category" page

  • The user fills out a form to create a new category, indicating their name and icon (both mandatory).
  • The user click (or taps) the "Save" button to create the new category, and is taken to the home page on success.
  • When the user clicks on the "Back" button (<), the user navigates to the home page.

• "Add a new transaction" page

  • The user fills out a form to create a new transaction with:
    • name (mandatory)
    • amount (mandatory)
    • categories (mandatory at least one)
  • The user click (or taps) the "Save" button to create the new category, and is taken to the transactions page for that category.
  • When the user clicks on the "Back" button (<), the user navigates to the transactions page for that category.

Testing requirements

• Create unit and integration tests for all the most important components of your RoR application.

Technical requirements

• You should use Postgres as your database.
• You should use devise for authentication.
• You should validate all user input to make sure that anyone with bad intentions cannot compromise your app.
• You can use a view template engine of your choice (.erb, .slim, .haml).
• The project should be deployed and accessible online.
• Your database schema should reflect the following structure:

Project documentation

Once you have finished the development of the project, you should record a video presenting the features of the project you built. It is a video with a maximum length of 5 minutes. The content of the video should include:

• a description of the project.
• a demo of the project features.
• you should also highlight some interesting piece of code or something you built that you are very proud of.

[descholar-ceo]

Hi @rbanos-mv 🤝 ,

Your project is complete! There is nothing else to say other than... it's time to merge it
Congratulations! 🎉

Highlights

👍🏽 Your project looks great ✔️

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

---

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.