Pretty Sweet Tech: Do Libraries Need Their Own App?

Recently I was asked an age old question: do libraries need their own app? To answer that, let’s take a look at how apps are made: The Life Cycle of an App:

1. An Idea is Born: Your library has identified a need in the community. You have explored different technology options to solve this need and discovered an app will reach the most people since more patrons own smartphones than computers.
2. Designing the App: You put your dream team together and brainstorm how this app will work. What are your main goals? What do you want people to get out of this app? How will the user interface look so it is easily navigated? There are many questions here. A simple navigation prototype in PowerPoint or on paper will work for getting ideas on paper.
3. Getting User Feedback: Describe your app idea to your target audience. Is there interest in the app? Would people use it? Which devices do users have? Which platform should the app be built upon? iOS? Android? Both?
4. Fundraising: Apps are not cheap to build. They take time to design, build and maintain over time. App development is a marathon, not a sprint. Depending on complexity, apps can take between $10,000 and over $200,000 for the initial build. Then $1,000 or more for monthly updates to keep the app working. More if you want a native built app across multiple platforms. Plus consulting fees.
5. Development: If you’re developing in-house, you need to identify existing staff, or bring on new staff to complete the project. If you’re using an outside company, you’ll probably need to use a bidding process, then communicate clearly with the company to let them know what you want. This process takes time and effort.
6. User Testing: It’s time to test your first build to see if it meets the need you intended. It may take time to raise awareness that the app exists and get people using it. User feedback can be tricky.
7. Updates/ Maintenance: A good developer can translate user feedback into workable updates for product improvement, without losing (m)any features.

All in all, a good app should suit a specific need, be well-designed for user navigation, and be updated regularly to retain users. Think about the apps on your phone. How many apps do you download and use consistently? What is the shelf-life of your apps? Which apps are competing for your attention? Think about what makes you repeatedly click an icon. Can your library design an app that will stand the test of time for your patrons? You won’t know until you try.