Author: teamfortitude

This week, our final week before halves, focused heavily on connections. This included both connecting the various parts of the project that the programmers have produced and connecting with others to help us playtest the texting app.

There weren’t any noticeably large design changes this week, though we conducted a lot of playtesting in order to figure out whether or not GoFundMe resonated with players as an indicator of the social standing of their character. We at first decided to go to playtesting night as per usual, but due to low attendance at playtest night, we couldn’t get the data we wanted. We decided instead to test with our classmates and faculty members at the ETC, conducting a total of 12 playtests on Friday. Unfortunately, the symbolism of GoFundMe did not seem to transfer over to the playtesters; instead of seeing it as a social indicator, they saw it as a second financial indicator, albeit a more abstract one. The design team is still discussing whether they will change the appearance of GoFundMe to make it appear more of a social indicator, or if they will instead embrace the way players currently see it and design based off of that.

Other things we learned from playtesting are as follows:

• Players originally didn’t notice that their text conversation had an impact on the GoFundMe, but a simple notification changed that.
• People have very different ideas about how to create a successful GoFundMe campaign, and most admit they would be unsure how to run a good one.
• The situation we tested was one where players had the choice to store undisclosed (presumably suspicious) items belonging to an old friend of theirs for $100 a week or not. 11 of the 12 players chose not to store the items, and were disappointed that they lost a friend in making that choice, but didn’t care deeply due to lack of knowledge of the strength of that relationship beforehand. We plan on fixing this by having the old friend reference an inside joke between the two characters before they present their situation.
• Some people felt uncomfortable making a final decision without getting more information about what the items to be stored were.
• Some people praised the interaction system and how realistic the diction felt.

Aside from responding to this feedback, the design team also refined the plan for the various clusters of content that will be released to the player throughout the game.

The programmers saw the finishing of some of the work from last week, connecting the texting app to the main view of the game, and using the database to provide the text in the conversations. A week’s worth of work and one long and grueling Friday night saw the seamless visual integration of these parts. There are still a couple known bugs with the display of the texts, and the bank app isn’t fully integrated yet, but significant progress has been made on both those fronts, and we feel like the prototype we have will be sufficient for halves.

In the art world, progress has been made on finalizing the layout of the notifications menu (which has tested well with playtesters), which included consulting with Shirley Yee, a typography expert, to make sure we are using good fonts. Shirley Yee confirmed that we are on a good track, and offered some ideas for minor improvements. The art team also made some images that will accompany news articles, as shown above.

Halves is days away, and Team Fortitude has accomplished a great amount of work in the development process. We’ve received plenty of feedback, the positive giving us the strength to keep pushing forward, and negative informing us how to fill the holes that must be filled to make Broke as strong as possible. We’re a team of determination and skill, and we’re ready to hear from the masses during our halves presentation on Wednesday. Thanks for reading, and we’ll see you next week!

This week saw a big step in the development, specifically because we’re moving into the stage that everyone has produced enough content for us to start connecting the different pieces we’ve made individually into one more cohesive app. We’ve interfaced a lot with each other, helped each other interface with content that other team members created, and helped players interface with the app.

The design of the game hasn’t gone through many huge changes this week, but we have been experimenting with the level of interaction players could potentially have with the characters in the game. Once again, we went to playtest night to get more data. We brought three text conversations to playtest night: one was a conversation with the player character’s father to decide whether or not to go to grad school, which only had one choice for the player (and therefore only one interactive moment), but it was a meaningful one. The second was a conversation where an old friend asked to pay you to store some of their things in your home, which had many choices, albeit not extremely significant ones. The third was a conversation with your addict sister, whose children were being taken away from her, and the player had to decide to either take her kids or let them go into the foster system. This conversation also had many choices, though the outcomes of them were much more significant. We asked playtesters to assess their feelings of freedom and satisfaction in the different conversations, regardless of the subject matter. Judging by the data we received, it seemed that players didn’t care so much about the nature of the decisions they had to make, but having any choice was better than having none. There were also some testers who were uncomfortable with the conversation with the addict sister, due to the very serious and heavy nature of the conversation and that no choice seemed like a very good answer. This is a feeling we want players to have, since these emotions best convey the struggle that those in poverty face, though this reaction has prompted us to save the majority of these types of conversations for later in the game, when there is less of a danger of players abandoning the game because it’s too heavy, when in truth they had only experienced a small, heavier than average slice of it.

Another question we’re still trying to answer is what the overarching goal of the game is. The strongest contenders are to either have no specific goal and see how well players do over a predetermined period of time or to have the game progress through the whole span of a GoFundMe fundraiser. The downside of the former is that our game may too closely mirror Spent, which has the same goal and play process. The downside of the latter is that it may reduce the needs of people in poverty to purely financial, and that all decisions boil down to money, when in reality these people live so much more complex lives. We plan on testing the use of a GoFundMe App as a relationship bank in the next phase of playtesting, so we can find out if players read it more as a social or financial indicator.

Aside from these major decisions, the design team has written more conversations that will take place in the texting app, which have been implemented into the game. The flow of the game has also been created; the game will be divided into three chunks, each starting with a news notification and ending with three conversations (two over text and one over email) that the player can play through in whichever order they please. Which conversations will happen in which chunk has also been decided.

As mentioned earlier, the programmers have begun to interface more with each other this week. The texting app is finished, work has been done on the player character profile (which internally keeps track of the player’s status with their finances and relationships), bank app, and the database that will keep track of player progress and all possible interactions the player could have with other characters in the app. The programmers have been working this week to connect these parts of the app into one cohesive final product. These connections also include connecting the work the designers do with the programming. The programmers will continue to work on this next week as well.

In the art world, work has been done on the layout of the news and email apps, figuring out exactly how and where information will be displayed for the players, as well as the various color schemes and art style.

We’re moving into halves territory, and while we still definitely have our work cut out for us, we feel like we’re on a good path to have a satisfactory amount of work done by the time halves comes in a week. We’ve made a lot of progress in development, and we’re confident that the faculty will realize that when we present the work we’ve done so far.

This week saw the continuation of development, but also saw a number of shifts in our design decisions based on feedback from playtesters and advisers. Though we didn’t expect the final visions of our game to change so much in just one week, we’re confident that our changes do not add significantly to the scope of the game, and will altogether result in a better end product.

The first event of the week that really changed the way we thought about the game was Sabrina Culyba coming in to play the original Poverty Spiral and learn about our interpretation for the mobile platform. As you may remember, Sabrina Culyba is the author of The Transformational Framework, and thus is an expert in using games as a tool to create change in the players. She was excited to work with us, and really brought in a new, fresh perspective of The Poverty Spiral.

A big takeaway we got from her was that as it stands now, our game focuses very much on a few individuals’ lives, instead of focusing on the systemic issues that let poverty pervade in our society. In other words, if we really want players to understand the big picture impact of poverty, we need to make some changes. We aren’t fully sure of any large changes we want to make to fix this, but for now we’re putting more focus on social impact in the news app and shifting the causes of the various situations in the game to focus more on external reasons rather than any of the characters involved being clearly to blame.

Another aspect of the game that Sabrina pointed out was the time taken to play. The time span of three days to play the game was something many faculty members were wary of due to scope reasons, but Sabrina had a different reason for disliking it: it makes the game harder for different players to discuss when they’re done. If two or more players who are friends need three days to finish the game, it’s very hard to guarantee that they’ll both be in the same room when they start and when they finish, making face-to-face discussion about the different decisions they made improbable. Sabrina suggested that we switch to an hour-long game that can be played all at once, players can compare face to face how the characters they played ended the game. We agree with her, and will now focus on an hour-long game. We suspect many faculty members will be very relieved by this decision.

Sabrina spoke highly of the board game version of The Poverty Spiral, and one thing she liked about that version was the spiral itself; it gave a very visual representation of how well a player was doing. Sabrina played as the homeless character, the most disadvantaged character in the game, and was very engaged by how much farther back in the spiral she moved, as well as how satisfying it made the victories when she moved farther out of the spiral, even if it was only for a brief moment and futile in the long run. In our version, statuses of finances and relationships are represented primarily numerically, which is much harder to visualize than the spiral. We agree that Sabrina has a point here (as she so often does). For now we’re going to represent the positions on the spiral with bars, but may change that later.

The final big takeaway we had from Sabrina was that a home screen may not be a good idea. Sabrina pointed out it may look empty if we can’t make more than five or six apps, and the current UI is so close to what one would find on an iOS device that players would frequently press the real home button and leave the game by accident. Incidents like this would likely take players out of the experience, so we’re going to switch to a notifications menu, which will more concisely display the different kinds of interactions players can do, while allowing for a more empty list of possible tasks if necessary.

Sabrina left the team a little overwhelmed with the novelty, validity, and magnitude of her feedback, leaving us wondering how we can change our design plan in so many ways, though our worry has calmed as we’ve invented solutions to the problems Sabrina discovered, and we realize that the scope of the project has not significantly increased, as we feared it may have to.

We learned a lot from playtesting the game with Sabrina, but just playtesting once wasn’t enough. On Wednesday night, the team took a trip up to main campus for our first playtest night. We got several undergrads to play two different stories from our mobile version of the game, currently in the form of the prototype we had for quarters. We came armed with a google form and got some great feedback. They related to the recent college grad character (about whom both of the situations we brought were written), and many understood the game’s central theme of poverty without being explicitly told that the game was about poverty. The big thing that didn’t land so well with them was that the interface and UI resembled that of iOS so closely that players often wanted to perform the actions they’d perform on their phones outside the game, like typing custom responses to messages, but they could not, because six people can’t replicate everything Apple has done in the span of five weeks. This further supported what Sabrina said about how we should change art styles, albeit for a different reason.

Development continued to progress this week. We figured out the code architecture for the app, and now know exactly how the apps all link together programmatically as well as how the decisions the player makes will affect their character’s profile and the future of the player’s experience. A lot of work has gone into developing these large-scale systems in the game, like app callback functions, middleware, view control and databases in which the content will be stored. More small-scale functions have also been programmed, like progression between situations within one app, and the display of texts within the texting app. A lot is still yet to come here, especially in the way of interaction, but we’ve put a lot of work into laying the foundation of the game.

Our designers have also been busy making the changes Sabrina pointed out, as well as creating more content for the text, news, and email apps. The designers have also been discussing when to end the game and how to incorporate privilege. Both of these have some proposed solutions; Dana, our client, proposed that the game can focus on the period of time that a GoFundMe campaign runs to get the player character something like a car, and the game starts and ends with that fundraiser. The designers have also discussed implementing privilege like a premium, limited currency in the game; in the event of difficult decisions, sometimes a third, obviously great decision will be available to the player, but they have to spend privilege points to use it. Privilege is very limited and precious in this game, forcing players to think carefully about when they use it.

Our artist has been revamping the art style of the game, changing it from one that mimics iOS. After conducting copious amounts of research, she proposed a style with a deep purple background, like in the board game, and UI with rough edges. Our client was very satisfied with her proposal, and we will likely take that style into the final game.

At the end of the week was the final major event, when Dana, our client, proposed that we change the name of the game. She proposed a few names, like Give Back the Refrigerator, which was perhaps the most memorable one, but we agreed on a new name proposed by the client that we all agreed was the best choice: Broke. It’s easily understandable, impactful, and short enough to appear under an app icon, and so we are now the developers of Broke.

So, our game is Broke. Despite the despair of the name, we’re stronger than ever coming out of this week, and are ready to give this new version of the game everything we’ve got.

This week was a big one for us, since we had our quarters presentation, during which we would show several ETC faculty members exactly what we’d accomplish so far and get feedback. This was also the week when we transitioned from pure research and design to development.

Our quarters presentation was the first thing we did this week, for which we prepared a short albeit densely packed presentation and a prototype of the texting app for the game. The presentation was made to give faculty a brief introduction into what the board game version of The Poverty Spiral does and how we plan to transfer that to a virtual phone. The prototype played through one section of dialogue, focusing on one situation card for the elderly character, in which the player’s son was kicked out by his wife due to a drinking problem, and players would have to decide whether to take in their son or not. Some faculty liked our game, praising our concept and player interactions. Some faculty didn’t like the nonlinear dialogue, citing that sometimes they would personally say something other than the pre-written responses. Some faculty thought we set our scope to be too big, prompting us to scale down to a one day experience with three playable characters, instead of a three to four day experience with six playable characters.

Now that we have the opinions of many faculty members recorded, we have started the programming for the app. Most of the work done on that front this week was figuring out the overall architecture of the app, researching how best to send push notifications on different operating systems, scaling the UI for any screen size, system design, data storage, and basic interactions of messages in the texting app.

A design document is also in the works for our game, which is listing the different content and interactions of the game so far.

We’ve also started to write dialogue for one playable character’s story (the recent college graduate), mapping how different decisions would affect their finances, relationships, and health. The situation cards have also been organized into piles corresponding to which character will experience those situations in the app.

While all these parts of the game were started, we did end the week with one finished product, and that was the team picture, shown below.

We’ve learned a lot this week about where our product stands and in what direction it’s currently going, and while it’s going to take more meetings with various faculty to make sure we head in the best possible direction, we have high hopes that we’re laying the foundation for something that will help a lot of people’s stories be told for the first time.

This was a slower week for Team Fortitude, since extremely cold weather and snow cost us two days of development. Nevertheless, we have made significant progress on our game, especially in finalizing our application of Sabrina Culyba’s Transformational Framework, and putting together the first prototype of our game.

The team finished reading the Transformational Framework, and went to a workshop led by the author, Sabrina Culyba. We were able to apply these principles of the framework to The Poverty Spiral, which we converted into a poster, shown below.

Sabrina Culyba also said she was interested in helping us out throughout the process, which was great news for us.

Using the knowledge and basic game design we have planned out so far, we were able to make a small prototype of the texting portion of the game using proto.io, a website useful for making prototypes of mobile apps, since it comes with all of the art assets Apple uses in the various interfaces of its apps. Our prototype presents a branching narrative that walks the player through one of the situation cards from the original board game, but instead of the situation being presented by one of the other players, it is revealed via the player character’s son, who is asking to stay with you, since his partner kicked him out for excessive drinking. The player then has to make a decision about how to respond to the situation directly to the character who would be most affected.

More situations like these are to come in future versions of the game, for which more documentation has been put together this week.

We also put together a broader picture of what our game will be by organizing the different apps we may include in the game. Here are our plans for each app:

• Texting will allow the player to carry out informal conversations with their character’s friends and family. These interactions will have the same format as the prototype we currently have, re-purposing the situation cards from the original board game.
• Email will work similarly to texting, but for more formal conversations with people like employers and landlords.
• Banking will help players keep track of their money, simulating their place on the poverty spiral.
• Health will give players a window into their character’s mental health, as well as information about information like current address (if any), emergency contacts, state of family members, health insurance, etc.
• News will replace social action cards, showing real-world events and policies that will affect how the characters live their lives.

The following apps are potential apps that may not make it into the final game, but we find have merit.

• To-Do List will list out mundane activities of the player character’s day.
• Calendar will list important events or appointments for the player character.
• GoFundMe will give a window into the player character’s relationship, since the amount of donations friends and family will make are reflective of how invested they are in that character.
• YouTube will show videos from interviews we’ve conducted with real people who have experienced poverty firsthand.
• Phone/Voicemail will let the player see different messages that other characters have left theirs.
• Music will show what kinds of music the player character listens to. This one will be more difficult due to copyright, but talks of creating original songs have been happening.

We’ve also been revamping the project website, logo, and poster, making sure that they reflects what our mission with the game as well as possible.

Next week is quarters for us, where we will present the current state of the project to faculty for review. We hope they will think that this game is going in the direction that will be the greatest benefit to those experiencing poverty as possible.

The second week of this project continued much of the research from last week, but there was also a lot of work done to finalize the direction of the game’s transition from board game to mobile game. We also made an effort to document the game as it stands now and figure out what parts of it were most essential to include in the mobile version we’re creating and started to create posters and logos for our team.

Like last week, we continued to research both what it’s like to live in poverty and the best methods for creating a transformational game. Much of the research done for learning more about the condition of poverty was done through reading relevant articles, literature, music, games, videos, and photographs. We also plan to interview people who have/do live through poverty, so as to answer some questions we have about living through the condition of poverty that either aren’t as explicit in our research or we want more personal answers to. We also hope to include recordings of some of these interviews in the final product, so players can see real people whose daily struggles are represented in the game. We’ve also gone deeper into Sabrina Culyba’s Transformational Framework, and outlined how to reflect the different aspects of the framework in our game.

A couple of us have also had the chance to try the game Frostpunk, a game where in an alternate future, London becomes inhospitable due to extreme blizzards. The player plays the role of the captain of a group of refugees who start to found a new city. The game’s presentation of a harsh reality and difficult decisions made it appear very relevant, and we found the game to be very engaging, even if there was some frustration that came from the events of the game. The game also had a progressing story throughout, which kept it interesting. However, some people criticized the game because many of the decisions took the form of saving one person or working to stop the entire city from freezing but in a slightly evil way. Some players said this was a very easy decision, since saving many people seemed much better than saving one. This led us to realize that like many of the other games we studied last week, there was still a space between the player and the characters; while the game gave everyone in the town a full name, face, profession, and dialogue, the player character had no relationship with anyone else in the city individually, which made the emotional impact of the decisions weaker. This further proved to us that establishing a strong relationship between the player and the characters is essential.

In order to figure out what parts of the game would be more important to the mobile version than others, we really had to break down the existing game. A lot of that went into the situation cards. We scanned them all into the computer, categorized them, made detailed spreadsheets about them, and analyzed them in a number of different aspects, like the broad nature of the decisions, what kind of player characters it applied to, which non-playable characters were affected by it, and the importance that each decision would have on the characters’ futures (e.g. not having a library card is much less important than not having a home). We also made a list of every single mechanical element of the game and presented them to our client in order to figure out what elements of the game were the most important to her. In general, she put a lot of importance on the aspects of the game that were made to reflect reality and making sure that every player character was exempt of assigned race or gender, so that any player could project themselves onto their character. The aspects she were the least attached to were those that existed mostly because the current platform was a board game; she definitely understood that playing to the platform of mobile devices was very important, and wanted to embrace the mobile platform as much as possible. We will definitely take her decisions on this matter to heart once we start creating the final product.

To figure out exactly what we would do going forward with the mobile platform and what kind of game we would be making, we presented two pitches to our client: A Virtual Phone, and The Relationship Spiral. A Virtual Phone has players take the role of someone in the condition of poverty, and gives them a phone with different apps. There would be a texting app, where friends and family would text the player the situations, and they’d have to respond to them (e.g. your daughter says she needs sanitary products, and you either tell her you’ll get some or not get any to save money), which we thought would seem more intimate than the way the situation cards currently play. There would also be a mobile banking app that would show the player’s current position on the spiral. A news app would function like the social impact cards. The Relationship Spiral was the same as the existing game, but with an additional element to motivate players to maintain their relationships. Players would be able to see a table with framed family photos on it. The photos would contain all the player character’s family members, and if the player made too many decisions at their expense, they would frown in the photos. If they made an egregious number of decisions that weren’t in any given family member’s favor, they would leave the player, fading out of the photos. Of the two, Dana preferred the first pitch, A Virtual Phone, since it fit the mobile platform better, and could still leave the player character’s gender and race more ambiguous. Thus, we will likely create A Virtual Phone.

This week really helped us learn exactly what aspects of The Poverty Spiral we wanted in the final product of our game, and made our direction much more concrete going into the development process.