After a meeting with Jeff and Quigley last week, the team has really jump-started our coding efforts. We’ve divided our pieces up so that by the end of this sprint, Sono will exist as a fully-formed app! The best part: every member of BadApp is learning something new, so that t the end of the day we will all walk away with new skills.
Daniel has been plugging away at the app’s main functionality, to record, save, mark, and edit Sono audio. Over the last sprint, he re-evaluated what was necessary for the app and what was just sufficient, and directed his program design considerations accordingly. What resulted was a complete overhaul in the abstraction layer of the application, which will allow for a fluid and seamless integration with the UI component.
After Daniel finished implementing the basic iPhone sound recording features, he began creating the features that make Sono intrinsically different from the rest. Testing will begin soon. For a limited time, reach out to us at email@example.com to be added to our alpha testing list.
Currently, Andrew is continuing to tweak the UI to anticipate any usability problems, thanks to lots of feedback from classmates, Jeff, and Quigley. A new logo has us all feeling pretty fancy as well:
In terms of usability, the team decided to have a bottom tab bar instead of a side-swipe menu to keep Sono down to as few pages as possible. Hannah Jane has been working on that, and is excited to contribute something coding-related to the project.
Lele has been working on the Settings page. This is where the user will be able to set things like their markback time, export options, and more. There are a lot of decisions to be made and this page will likely change a lot throughout the rest of the sprint, but having such an important piece of the app done will be great.
To the average viewer the settings page may seem like something uninteresting, as it lacks the splash and shine of the other UI designs, but it holds the key to maximum functionality which makes Sono that much more special. Even before the groupings and ordering of the settings page could be created the extensive task of determining what the user should be able to customize came first. Everything from keeping the screen lit during recording, to choosing the destination folder settings had to be mapped to our current screens and mapped to future implementations. The creation of the setting screen also helped the group Sono decide what fine details we could implement and polish up in Sono.
Jenny has been working on a tutorial and about page, which will help our user experience by quickly explaining the different working parts of the app. The tutorial will include multiple screens giving the user instruction on the different functions and pages of Sono. The About page will be accessible from the bottom tabbed menu, and will pull information directly from Sono’s website. It looks great so far, and we’re excited to get feedback from others about the clarity of the app.
We have a working website that has both a front-end and an administrator back-end. HJ wanted to use Joomla! for content management because of the ease of use combined with the amount of flexibility . It took forever to get it correctly set up, but now the team has a bare-bones platform for sharing information that is all their own.
After getting all these pieces in order, it will be nerve-wracking to see what happens when we combine everything. But by next week’s end-of-sprint demo, we should have a functional and beautiful product that only needs some tweaking before we wow the crowd on Demo Day!