This needs to be created using Android studio, using Java, This program also needs to use fragments.

You are charged with the responsibility of creating a simple "Game Character Creation" interface, giving the user the ability to set the default values of different character types. It is assumed you will use good software engineering practice throughout, including the following: Use comments (useful comments), including your name, instructor's name, class you are in, and which project this is at the top of your Main Activity Java file . Give appropriate ids to your widgets o Buttom, button2, etc. will result in loss of points For each character class is listed in a list. Note that this doesn't mean "class" in the OOP sense - a "class" in traditional role playing games, and other games, means the profession or type of character (which then denotes that character's skills in different areas, etc.) Each character has a total of 1o points to spend on 4 different attributes: . Strength Intellect Wisdom Dexterity ON A SMALLER DEVICE Warrior Warrior Mage Healer Hunter Paladin Strength Intellect on selection of list item Wisdom Dexterity Points left to spend: 0 Note that separate character professions/classes will result in a new activity being launched with the information displayed ON A LARGER DEVICE Warrion Warrior Mage Healer Hunter Paladin Strength Intellect Wisdom Dexterity Points left to spend: 0 Because larger devices have more screen real estate, the activity remains the same, but instead you use fragments to load/change only the right side of the screen to display the appropriate character information GENERAL REQUIREMENTS You should ensure your program and assignment adhere to the following (In fact you could use the following, keeping the above instructions in mind also, as a check list) You must use fragments O There must be a total of 10 points to spend for each character class o The user can navigate away without spending any, or spending all o The user cannot ever spend more than 10 points in total You must use the RatingBar widget for the star icons to denote the number of points spent on each attribute The app must display the "points left to spend" at the bottom (or the top - you can make small modifications to the interface.) The app must save the points spent on each attribute using SharedPreferences When the user navigates to and from different character classes, the spent points and related data must save and load the appropriate values, respectively