Our first focus was on the development of a mobile Web-based platform because we wanted the content to work across all mobile platforms [6]. Identification of the most viewed information was carried out using in-house analytic data coupled with the Google Analytics service configured for the ALSoD website. The Google Analytics tool was configured in August 2012. We based our data analysis on the 3 subsequent months (August, September, and October). These represent the period from when the Google Analytics tool was implemented to the point where we started the development of the mobile website and will be referred to as the pre-mobile website period. The 3-month period from November 2012 to January 2013 with the mobile website fully developed and the app implemented will be referred to as the post-mobile website period. In the pre-mobile website period, page views (the total number of pages viewed) were analyzed to discover the commonly visited pages on the website, including repeated views of a single page.

Designing a mobile website that works on several platforms does not mean shrinking a complete webpage into a mini-sized webpage; the aim is to eliminate very small type, scrolling left or right, and typing, and to achieve the outcome required with a single click [6,15]. We therefore created a separate style sheet, retained some original images, reduced the size of images by a fixed percentage, configured the content layout of the screen to wrap text, and summarized the information on the desktop version to fit a smaller screen.

To detect if the request comes from a mobile device, the .NET Framework provides the “isMobileDevice” property, which returns a true value if the browser is a recognized mobile device. This does not always work because some mobile device browsers disguise themselves as desktop browsers [16]. We therefore use “UserAgent” strings sent by the mobile device browser to the server in conjunction with the “isMobileDevice”, as described in Multimedia Appendix 1 and with an overview in Figure 1.

Text messages and BlackBerry Messenger messages were sent to a selection of individuals known to the authors, asking them to view the ALSoD Web address on their phones and tablets. After the app was developed, additional users were asked to download the app via Google Play. Since ALSoD has a Facebook [17] account, a Facebook “Recommend” Button was embedded on the mobile master page. All users were asked to click on the Facebook Recommend button so as to have an estimate of the number of users who were satisfied with the outcome of the display on their phone, as seen in Figure 2.

The most commonly used smartphone platforms are iOS, BlackBerry, Android, and Windows Mobile. We used Eclipse software as the integrated development environment (IDE), with the Android software development kit (SDK), Android development tools (ADT) plugin, BlackBerry plugin, and the latest SDK tools and platforms, downloaded using the SDK Manager [18-22].

From Eclipse, the application was compiled producing an .apk file (Android application package file format). This file was submitted to a registered Google Play account with a generated keystore containing a private key [23]. The ALSoD app can be downloaded from Google Play and currently, our Google app account confirms that the ALSoD app has had more than 100 downloads. The app then displays the website (designed using the Microsoft ASP.NET framework) with no status bar or URL navigation on the screen.

A marquee function scrolling text from right to left was inserted on the desktop master page to create an alert for regular users of the website, as seen in Figure 3. At symposiums and seminars, researchers were exposed to the recent development of the mobile app, which has contributed to increased Web traffic to ALSoD.

During the various presentations of the mobile app development through posters and seminars, practical assessment of the website on mobile phones was carried out by attendants. Responses, questions asked, concerns raised, and critical analysis given by the audience were recorded and considered.

The Google Analytics account for ALSoD was created in August 2012 to compare results generated by the two tools (mobile website and app) and to gain insight into the changes of the design and content of the website [24]. Visits were compared for the period before mobile website development, from August 2012 to October 2012, with the period after, from November 2012 to January 2013.

In the 6-month data analysis period from August 2012 to January 2013, there were 5051 visits to the website, of which 2698 were unique (53%). There were 19,785 page views, of which 8883 (45%) were to 4 sets of pages. These pages focused on the pathogenicity of mutations, gene information, data analysis of mutations, and patient data.

Pages were optimized for mobile browsing by reducing image size to 5% of the original size, creating a mobile master page different from the desktop master page, and creating a link page to allow users to switch seamlessly between the mobile and desktop views.

If the UserAgent string contained keywords suggesting a mobile platform, for example, BlackBerry, Palm, mobile, iPhone, or iPad, then the user’s device was redirected to the mobile site [25] displaying the compact version (Figure 2) of the website instead of the full version (Figure 3) [11].

To test this, we sent the mobile site URL to mobile phones of 14 users (colleagues and friends from whom we could easily obtain verbal feedback): 3 on the Android platform, 1 on the Windows Phone, 5 on BlackBerry OS, and 5 on iOS (2 iPhone and 3 iPad). All users gave positive feedback except for the Windows Phone user who could not utilize the pages with dropdown boxes.

Following successful implementation of the mobile website, we began app development. One straightforward method to achieve this is to automatically convert an already-built mobile website into a native app. This is done through the “WebView” object, which is an in-app Web browser used to display a website as if viewed on the browser of an Android smartphone [11]. For testing, we downloaded and used Android simulators. The plugins allow programmers to develop, test, and debug a Java application using the Eclipse IDE, but it requires a high level of programming skill [26]. We also tested and manipulated the .apk file on a real Android phone before submitting to Google Play.

Following the development of the mobile version, on the ALSoD Facebook page, 34 users recommended the website by May 29, 2013, using the Facebook “Recommend” button embedded on the website. Current tabular data are available on the website [27], displaying the growth of visits to the genetic database, as seen graphically in Figure 4.

After the creation, testing, and publicity of the app, we received feedback from users about: caching for offline viewing [28-30], which would enable users to continue work; having a “page loading” icon when connecting; making users aware of the cookies policy; using an option menu button [31] to display analysis webpages (interaction.aspx, credibility.aspx, analysis.aspx); and creating a link to allow users to switch from mobile view to desktop view, as this would be useful on tablets like the iPad. We were able to implement all changes except for the offline viewing, which is difficult to implement because the database is large and held online.

Our Google Analytics account showed that visits to the website increased from 2231 to 2820, yielding a 26% increase from pre-mobile period to post-mobile period and a 230% increase on the use of mobile devices (including tablets) to access the ALSoD website. On average, there were 300 unique visitors a day suggesting a high demand from the research community. A total of 1595 unique visitors in the post-mobile era accessed 11,376 page views on the website as opposed to 1220 unique visitors in the pre-mobile period (an increase of 31%), showing the relevance of a mobile-friendly website. Five mobile operating systems (Android, iOS, BlackBerry, Windows Phone, Symbian) were detected to have accessed the website within 6 months. Although BlackBerry OS visits declined from 34 to 14 visits (58%), iOS for iPhones and iPads increased from 40 to 105 visits (162%), and visits by Android devices increased from 29 to 213 visits (634%) (see Table 1). The Google search engine was the most used to search for the website (see Table 2). The likely explanation for the great increase in the use of Android devices is the development and introduction of the Android app submitted to Google Play.

ALSoD was developed as a disease-specific database for ALS, focused on genetics and phenotype, with planned incorporation of environmental and other risk factors in the future. We have shown that development of the website to facilitate smartphone access has greatly increased access.

In broad terms, there are two strategies for development of an app like this. Either the app can be developed as stand-alone software or it can be developed as a means to access an existing mobile website. We chose access to a mobile website for several reasons. First, we used this approach because mobile websites are immediately accessible to users through a browser, more compatible across devices, have easier content updates, are faster to find on search engines, make it easier to share content via a link, have a longer lifecycle on a user’s device, are easily convertible to an app, and are more cost-effective [14,32]. Second, the database is regularly updated with data, which would require the release of weekly updates to an app if the website was not the primary content holder. Third, although third-party automated app development tools exist [33,34], it was simple for us to convert the mobile website into an Android app using the WebView object.

A limitation to this approach is that the website recognizes a mobile device based on the information held in the list in the UserAgents string. Although software exists to automatically update the list, there is a financial cost involved and we have therefore chosen to update the list manually. Furthermore, UserAgents strings are limited in the kind of information sent to the server. Specific information such as the size of the screen, the manufacturer, the format of image supported, and the model of phone are not sent. This is an issue because some mobile devices allow portrait and landscape views when repositioned while others have unique width and height dimensions. It is therefore difficult to have a perfect display on all devices.

There are 3 main methods by which users access the website (Table 2). Roughly 39% of the traffic is organic from the Google search engine, 37% is direct by typing the ALSoD URL directly on a browser, and the rest are referrals through external sites collaborating with ALSoD.

More than 100 interactive, downloadable widgets and mobile applications have been submitted to the NHS Choices Health Apps library [35]. Some of these apps are commercial apps and the freely available ones range from calculating alcohol consumption to weight tracking. There are no specific genetics disease apps that concentrate on combining genotype, phenotype, and geographical information with associated analysis tools, although ALS database apps do exist. For example, the PatientsLikeMe app was initially developed to help United Kingdom-based ALS patients find clinical trials that are right for them and organizations find patients right for their trials [36,37]. The ALSoD app has direct relevance to clinicians working in ALS and therefore relevance to the NHS Choices Health Apps library. It includes a comparison tool to evaluate information for different genes side by side or jointly with user configurable features, a pathogenicity prediction tool using a combination of computational approaches to distinguish variants with nonfunctional characteristics from disease-associated mutations with more dangerous consequences, and a credibility tool to enable ALS clinicians and researchers to objectively assess the evidence for gene-causation in ALS. A checklist, as seen in Multimedia Appendix 2, was used to report the web-based intervention of users [38]. Furthermore, integration of external tools, systems for feedback, annotation by users, and two-way links to collaborators hosting complementary databases further enhance the functionality.

Development of the mobile website and associated app has increased access to this disease-specific database and facilitated access through a wide range of devices. Visitor analysis has shown the importance of collaborating with other relevant databases through hyperlinks. Our future work will concentrate on further integration with other databases, adding in nongenetic risk factors, and increasing access and relevance for related research disciplines.