Board Thread:Administrative Discussions/@comment-1824272-20150205084333/@comment-1824272-20150206020458

Let me try to clear something up: We're not hiring programmers to design an app, nor are we designing an app for anything besides Acepedia, nor are we even designing an app at all.

Community Apps are designed and run by Wikia themselves, the guys who are running the service that we're using. If we created a Community App for Acepedia, it would allow users to quickly access any article they desired.

However, a Community App is NOT the same as the mobile browser or what it can do. You cannot see the forum, comments, or user pages on the Community App, nor can you chat with users, nor can you edit pages nor can you log in. The point of the Community App is to get our articles to mobile devices on Google Play / iOS Store so we can reach a wider audience on a native app. It's not for anything besides reading the articles themselves.

To see what Acepedia would look like on a Community App, you can download the Game Guides app. It's essentially the same thing, but Game Guides allows you to browse through all of the gaming wikias, not just ours. The question about the Community App is whether you guys think we should pursue and advertise our own app for people to download, or just advertise the Game Guides app, or neither and just focus on the mobile browser experience instead of apps. Personally, I think getting our own app would still be really cool, and it's identical to Game Guides which we're on no matter what and still have to take into account anyway.