Palbetto Case Study

Overview

Palbetto is an app that would function specifically to allow a Game Master/Dungeon Master (herein referred to as a “DM”) of Tabletop Roleplaying games to better connect with and coordinate session times with players in campaigns that they’re currently hosting. The app enables DMs to proactively set their availability and coordinate it with their existing party of players to ensure that sessions are able to be held at regular intervals.

Problem Statement

Turn-based RPGs – in the style of Final Fantasy, Dragon Quest, and similar titles – are considered outdated by many of gamers. Many in my personal circle have told me they find playing such games tiring and repetitive. A specific gamer, who enjoyed such games when they were younger, even disclosed to me that they found replaying a Final Fantasy game from the 90s as an adult exhausting. Common complaints include the gameplay also being slow.

The aim then becomes to create a battle system that can counter these issues. It must be challenging, and engaging, with the potential for fast-paced gameplay that drives players to keep going.

Users and Audience

The audience would be gamers who enjoy (or once enjoyed) turn-based RPGs; gamers over age 36. In some instances, there may be gamers outside that age demographic who enjoy this exact genre but they’re a lot less common.

Scope & Constraints

Typical constraints apply, as this is a one-person project. However, a big one looms on the horizon: modern gamers are very discerning, critical, meticulous, and often unforgiving.

Process & Actions Taken

Phase 1

Working from the original notes and rough mockup, I went about making some rough sketches of aspects of the HUD and UI to flesh out a base concept. I also went about making rough sketches for the sprites (individual pixel artwork of player characters and example enemies)

Phase 2

The Designer created a concept using Adobe XD, trying to realize the overall form of the application.

When a user signs up, they will be able to select whether they will be using Palbetto as a DM, a player, or both.

Self-explanatory, this is where users would edit their basic information as it displays on the app to other users.

If a user's account is set up to function only as a DM/GM, the DM tools section will display on Home.

If a user's account is set up to function only as a Player, the Active Player Campaigns section will display on Home instead.

If a user's account is set up to be both a DM/GM and a player, then both will display.

DMs will be able to request their players' schedules by selecting the week they wish to hold the session. Doing this will send a notification to players asking them to indicate their availability for the week the DM selected.

As a player responding to a schedule request, players will set the times they're available for a tabletop session during the days of the selected week.

Clicking a specific day will bring up a prompt allowing the player to enter their available time slots for the day.

If a player hasn't selected a time slot, the 'Not Available' option will display and they will be able to tick it in lieu of entering any times.

This page allows a DM to see an overview of their party.

If players' schedules overlap, Palbetto will display the time slots where they do. From there the DM can select a day and time slot to finalize scheduling their session.

After selecting the desired time slot, the DM can specify the finalized times for the session.

When the finalized time is submitted, the DM will get this message.

If the schedules of all of the players do not overlap, the DM will get this message. The app will not *actually* yell at the players, but it will send them a sternly worded email regarding the issue.

Phase 3

Examples of the type and frequency of push notifications would send users were generated.

The frequency of notifications will differ in the finalized application based on user testing. They will get more passive-aggressive the longer a user ignores them.