AO3 News

Post Header

Banner by Diane with the outlines of a man and woman speaking with word bubbles, one of which has the OTW logo and the other which says 'OTW Announcement'

An unofficial Archive of Our Own Android app was recently released to Google Play. As this release has brought the subject back into the spotlight, we wanted to take this opportunity to share the current state of official AO3 app development.

"Have you thought about making an app?" is one of our most frequently asked questions, but in mobile app development, there isn’t actually such a thing as "an" app. Apps need to be built for different mobile platforms -- Android, iOS, and Windows Mobile being the top three -- and for the many versions of those platforms still in use.

Before we could even start developing an app that would allow you to do anything more than browse unrestricted works, we would need to develop a public API -- definitely on our roadmap, but several major releases away. Then, we would need to build different, responsive user interfaces for both phone and tablet. What seems like a small, straightforward project evolves very quickly into something needing many resources, dedicated ones, with diverse skill-sets. While we have said in the past that we'd like to release a mobile AO3 app, the required resources just aren't available.

The coders who develop the Archive all do so on a volunteer basis, and give as much time as possible to support its growth -- but that time is limited, and fully consumed by the work needed to keep the Archive running smoothly. Either the team spends time continuing to improve the Archive, or developing an app -- there simply aren't enough volunteers to support both.

It’s not just the initial development that would be resource-intensive. An app would need to be maintained and continually updated to ensure it keeps working as new versions of each platform are released -- not to mention enhancing the app to include new and improved Archive features! And because an app would require long-term maintenance by a dedicated team, it’s not something we can reliably fund with donations.

But coding and testing resources don't even begin to scratch the surface of what would be needed to support an app! Resources would also be needed from the following teams:

  • Support would need to be staffed, trained, and equipped to help with any technical issues encountered on each platform,
  • Our Documentation team would have to create and continually update support documents for the app, and
  • The Translation team would have to translate and continually update the documentation to make the app accessible to non-English speakers.

Not only would this be more resources than we currently have available, it would also pull team members away from working in support of our roadmap.

Our team's goal is to keep the Archive available and accessible to as many people as possible. The best way we can do so is by focusing our efforts on building a single, responsive version of the Archive that works (and works well!) on as many devices as possible. We are eternally dedicated to ensuring that this includes devices of all shapes and sizes, and will continue to focus resources on enhancing the site's mobile responsiveness and usability for all. That means a standalone app just isn't possible at this point in the Archive's development.

To close on a security note, if a third-party app or website requests your AO3 login information, please proceed cautiously and be aware that you are providing this information at your own risk. While there are no current security concerns, please be sure to change your password if you believe your account may have been compromised at any time.