Skip to content

Rest API Server and Client applications that allow users to track calories

Notifications You must be signed in to change notification settings

vladimirslav/Calorie-Tracker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Simple calorie tracker I did for the interview. Uses PHP / MySQL / JavaScript / HTML5 / CSS
Initial requirements:
    -User must be able to create an account and log in
    -When logged in, user can see a list of his meals and calories (user enters calories manually, no auto calculations!), also he should be able to edit and delete
    -Implement at least two roles with different permission levels (ie: a regular user would only be able to CRUD on his owned records, a user manager would be able to CRUD users, an admin would be able to CRUD on all records and users, etc.)
    -Each entry has a date, time, text, and num of calories
    -Filter by dates from-to, time from-to (e.g. how much calories have I had for lunch each day in the last month, if lunch is between 12 and 15h)
    -User setting – Expected number of calories per day
    -When displayed, it goes green if the total for that day is less than expected number of calories per day, otherwise goes red
    -Minimal UI/UX design is needed.
    -All actions need to be done client side using AJAX, refreshing the page is not acceptable. (If a mobile app, disregard this)
    -REST API. Make it possible to perform all user actions via the API, including authentication (If a mobile application and you don’t know how to create your own backend you can use Parse.com, Firebase.com or similar services to create the API).
    -In any case you should be able to explain how a REST API works and demonstrate that by creating functional tests that use the REST Layer directly.
    -Bonus: unit and e2e tests!
    -You will not be marked on graphic design, however, do try to keep it as tidy as possible.


Initial Estimate:
- Planning                                                 3h
- REST API                                                11h
    - Basic protocol / endpoint parsing            3h
    - Account Creation / User Role / Logon system: 4h
    - Meal/Calorie CRUD:                           2h
    - Meal/Calorie filtering                       2h
- GUI :                                                   10h
- Tests (unit and e2e):                                    4h
- Documentation:                                           2h
____________________________
Total:                                                    30h

About

Rest API Server and Client applications that allow users to track calories

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages