Project 2: Milestone 2

Digital Prototyping and Psuedocode

After making rough sketches of the design using note cards, I began to assemble a base framework for how the app will function. This included making a (character) selection activity view and a fragmented tabbed view (for that character’s stats). From the selection screen, the user will be able to create a new character by entering a name and class.

Originally, I was gonna have their level determine all the base stats automatically, but I lack sufficient knowledge on Dungeons and Dragons to accurately implement that. Instead, the app will function as a digital player sheet and dice roller which is easy to edit and navigate through. The dice roller might be a implicit intent to another site which already has its own dice rolling algorithms.

While I still need to organize and implement a data model for passing all the character info between views effectively, I’ve at least made progress by setting up the list of selections which takes the user to a tabbed activity view.

This is a good framework, but the real challenge will come with passing character data between these two views and the respective fragments which will compose the character sheet activity. While it’s possible to pass custom serializable classes using intent extras, getting all the information to the proper fragment activities might prove problematic.

I also need to find a way to add new characters to the selection menu using a simple character creation activity. This view will initialize the character’s profile with a name and class type, then add it to the list of characters in the main activity. The floating icon buttons within each activity use explicit and implicit intents to load the character creation screen and online dice roller respectively.