Persist :: Becky Sippert
The problem my app solves is keeping track of scores for the card game 500, since it can be difficult to remember which bids get what point value.
The app has three screens. The first displays the bids (READ) that have been made in the game, the total scores of either team, and buttons that let you start a new game and make a new bid.
The second screen is where the bid is made. The user chooses the team that made the bid, the number of tricks they can take, and the suit they can take it in. The “Enter Bid” button takes the user to the last screen.
The last screen is where the actual number of tricks taken is recorded, using two rating bars near the bottom. The “Enter Score” button takes the user back to the first screen and inserts the bid into the table (CREATE).
The first screen also has functionality to UPDATE and DELETE the bids from the bid table. To update you click a bid list item, which takes you through the other two screens and updates the bid rather than creating a new one. To delete a bid, you long click a bid list item.
Developing this app taught me that it’s difficult to try to get complex layouts to work in both screen orientations, and you should try and keep models and database designs as simple as they can be.
