This past week, the team at DevCodeCamp has been making great progress on the Beepods Hive Inspection App! They have now made it possible for users to log into their Beepods account using the app, so all of their data can be synced. This will also allow us to look at who is using the app so that we can know where to store which inspection forms.
The question and selection screens are also coming along nicely – so much so that we are hoping to be able to begin user testing within a couple of weeks!
Next, the team is now able to access the database that they created for Beepods through an expansion of a WordPress API (application program interface), which they also created! The purpose of this is to be able to pull yard and hive data for analysis, as well as to allow users to manage their hives. By “manage,” we mean updating the address of your hive if you decide to move, add or remove hives from yards, and giving other users access to view, edit, or add data to a hive or yard that you are the owner of.
Below are a couple of examples of what the final hive and yard settings screens may look like:
From this screen, users will be able to add or remove hives. They will also be able to add or remove other users from their yard and/or hive. While latitude and longitude are visible on this example, they will not be visible in the final app. They are visible here for testing purposes only, and will allow us to use a user’s entered address for future features on the app that will require geolocation.
Below are a few examples of questions that will make up the hive inspection form:
The design here is extremely simple, because we want to make this app as easy for our users to operate as possible. The app developers decided to keep the number of options on the screen to a minimum so that users can easily navigate the screens one-handed, since we know that beekeepers rarely have both hands free during inspections.
As a user answers the questions on their screen, the form will automatically move on to the next question (no need to tap a “next” button!). There will also eventually be a header, as well as a back button in case you need to revisit a question.
Next is an example of how the yard selection screen may look. Each yard has a name (in this example, they are named after Taylor Swift albums) so that the user can easily find which yard they are looking for. Users will have the option to choose the names of their yards, so they can name the yard whatever makes the most sense to them.
Finally, we’d like to introduce you to another member of the app development team:
Aaron is a pillow fight world record holder. He routinely makes it to the third round of spelling bees, and at one point could match every country to its flag. As a burgeoning full-stack developer, he particularly enjoys solving and implementing back-end solutions. He hopes to one day appear on the front page of Google search results.