# Discourse as Android Application
**URL:** https://meta.discourse.org/t/discourse-as-android-application/22919
**Category:** Feature
**Created:** [2014年十二月6日 13:03 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919 "2014-12-06T13:03:49Z")
**Posts on this page:** 15
**Page:** 4
### Author:  [@alefattorini](https://meta.discourse.org/u/alefattorini)
#### Post date: [2015年四月1日 07:28 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/62 "2015-04-01T07:28:02Z")
> [@mbs](#):
>
> So do I, but I cannot ask people who only check their e-mails once a month to check if they’ve been invited to a beta to change their wrong habits.
Totally agree with you, we can’t undervalue this aspect
---
### Author:  [@rumpelsepp](https://meta.discourse.org/u/rumpelsepp)
#### Post date: [2015年四月1日 08:10 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/63 "2015-04-01T08:10:06Z")
> [@mbs](#):
>
> So do I, but I cannot ask people who only check their e-mails once a month to check if they’ve been invited to a beta to change their wrong habits.
And you are sure that they will check the discourse push notifications rather than email push notifications? But this is just bikeshedding, sry… I’m out.
---
### Author:  [@mbs](https://meta.discourse.org/u/mbs)
#### Post date: [2015年四月1日 08:42 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/64 "2015-04-01T08:42:45Z")
> [@rumpelsepp](#):
>
> And you are sure that they will check the discourse push notifications rather than email push notifications? But this is just bikeshedding, sry… I’m out.
Actually, yes. That’s the current standard for smartphone interaction, mostly through apps like Whatsapp, Telegram, Facebook both notifications and messenger.
Youngsters on mobile are used to being notified that way, so it is only normal that’s what they expect.
Not everyone uses e-mail, I know for a fact many of my friends don’t, as I am still in my twenties and I see on a daily basis how people use their mobile. It differs from my use, but I’m a minority and they’re the high percentage.
Your points may be correct when considering your point of view, but one has to understand there’s plenty different, and sometimes it is worth seconding others’ views and habits.
---
### Author:  [@purldator](https://meta.discourse.org/u/purldator)
#### Post date: [2015年四月1日 09:20 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/65 "2015-04-01T09:20:02Z")
To add what you already mentioned: Emails add a single ‘receipt’ for every notification. That is overkill for some power users. In fact, I currently have Meta here to send me no emails. I would fully prefer push notifications so I am still alerted without having Discourse in a tab on my browser. I have Discourse in a tab when possible but I’d honestly rather _not_ because with push notifs that’s one less tab eating my RAM. Also, as of right now, all I have for a real-time papertrail-less new activity indicator is the favicon numeral-count. It tells me nothing else, so when I see a number I go to check and find out the new topics and replies are something that A. is not relevant to me or B. something I could honestly check later. I have ADHD so I personally need more of ‘what’ the new posts are so I don’t break my workflow to constantly check the open Discourse tab. Push notifs allow me to have more ‘mental freedom’ and less anxiety wondering if I’ll miss something as it happens. I use push notifs this exact way for gmail and I can say that it has reduced my stress, anxiety and I no longer worry exactly _what_ is new. So I check less.
Furthermore, with services like Pushbullet, I get everything from my mobile onto my laptop. With what I mentioned above, I can integrate both my Nexus and my laptop together with Pushbullet.
Coupled with the fact that I plan on opening at least two Discourse instances, all those extra tabs add up, plus the checking anxiety.
---
### Author:  [@downey](https://meta.discourse.org/u/downey)
#### Post date: [2015年四月1日 12:52 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/66 "2015-04-01T12:52:27Z")
> [@Moter8](#):
>
> I think a “generic” solution is more important to create than a single-service focused one.
QFT; this is really important. Using Pushbullet or any proprietary service platform is a Bad Idea for an open source project.
Said proprietary service could go away overnight, change its terms of service to exclude parts of the world, or decide to fork a copy of all its data to the NSA.
Standards exist for mobile notifications on the various OS options. Compatible open source solutions should be made to work with them, to ensure long term sustainability and access to everyone.
---
### Author:  [@BCHK](https://meta.discourse.org/u/BCHK)
#### Post date: [2015年四月21日 17:09 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/67 "2015-04-21T17:09:33Z")
> [@downey](#):
>
> Said proprietary service could go away overnight, change its terms of service to exclude parts of the world, or decide to fork a copy of all its data to the NSA.
>
> Standards exist for mobile notifications on the various OS options.
Folks - I’m getting close to moving forward on this. My plan is to do this as a private effort that I will keep private for a year or so - then ultimately push it out to the public domain.
The plan is to initially do an Android app, then an Iphone app immediately following that.
I’d like to keep it as open source as possible - so if there is a good open source notification approach, please let me know. Otherwise we may go with the proprietary solutions for expediency sake.
Also - if we go with the webview approach for the forum which seems like the best immediate approach, are there good approaches that are recommended for caching, or pre-fetching (scheduled fetching) of messages so as to minimize the delay / time lag of seeing the more current messages at app launch time?
Any feedback appreciated. I’m going to be working with a contract developer on this project - I’m not the developer myself, but I’m busy developing the app specification.
---
### Author:  [@Tom\_Newsom](https://meta.discourse.org/u/Tom_Newsom)
#### Post date: [2015年四月24日 10:31 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/68 "2015-04-24T10:31:19Z")
Plenty of options availlable. This Stack Overflow thread is a good place to start, but Pushd seem to be the best at a casual glance
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [2015年五月5日 11:27 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/69 "2015-05-05T11:27:47Z")
There’s a new “magic app creator” in town called Manifold.js
> **[Generate Cross‑Platform PWAs Easily with ManifoldJS](https://www.manifoldjs.com/)**
>
> ManifoldJS (now PWA Builder) helps you generate cross‑platform Progressive Web Apps effortlessly—either via web wizard or CLI—from a URL or W3C manifest.
[http://blogs.msdn.com/b/johnshews\_blog/archive/2015/04/30/build-2015-and-manifoldjs.aspx](http://blogs.msdn.com/b/johnshews_blog/archive/2015/04/30/build-2015-and-manifoldjs.aspx)
My basic understanding of it after a quick read is that it assists you in the process of wrapping up your web app for native platforms. The more compliant your app is with the [Manifest for Web Apps](http://www.w3.org/TR/appmanifest/) the better. It will attempt to fill any missing gaps by using Cordova.
There’s an on-site generator that you can feed live web apps to, and Discourse fared pretty well. It just wants a bunch of extra icons added.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2015年五月5日 23:39 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/70 "2015-05-05T23:39:21Z")
Note that Discourse doesn’t use an appcache manifest at all, though it might do well with one - would just need to make sure to timestamp the PreloadStore values, I think.
---
### Author:  [@michel\_slm](https://meta.discourse.org/u/michel_slm)
#### Post date: [2015年六月17日 08:29 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/71 "2015-06-17T08:29:09Z")
That would be great. Right now adding Discourse sites to my homescreen still launches them as a normal browser window, with URL bar and everything.
[Adding manifests](https://developers.google.com/web/updates/2014/11/Support-for-installable-web-apps-with-webapp-manifest-in-chrome-38-for-Android?hl=en) would definitely improve the experience.
---
### Author:  [@Nilesh\_Trivedi](https://meta.discourse.org/u/Nilesh_Trivedi)
#### Post date: [2015年七月29日 07:39 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/72 "2015-07-29T07:39:00Z")
I am working with Government of India and considering using Discourse for civic discussion and open governance in a rural district in India. Discourse as a website is NOT good enough. Moreover, the Android app that was linked a couple of times above, is NOT available anymore.
Villagers in India whose only network access is their 100$ smartphone, do NOT have or do NOT understand e-mail. They understand signing up using their phone number, which isn’t easy to enable in a Discourse install. When Discourse sends notifications on email, it will open their E-mail app, not the Discourse app, causing further friction. Adding a website to homescreen is also something has some friction and therefore not many people do that, even though it is supposed to be easy. These users are also very price-sensitive and would want to minimize data usage for this app, but for now, I am assuming that Discourse website already handles it well using caching.
So, a Discourse app, even based on webview, would be amazing.
---
### Author:  [@downey](https://meta.discourse.org/u/downey)
#### Post date: [2015年七月29日 16:36 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/73 "2015-07-29T16:36:42Z")
Some useful data from the 2nd quarter of 2015 that is related to mobile web demand vs. mobile app demand:
For example, Asia is 90% mobile web usage and 10% app usage. Africa leans toward web even higher, and Middle East falls just behind Asia.
The US and Australia are the only places where app use exceeds mobile web use.
Full report: [https://operamediaworks.com/innovation-and-insights/state-of-mobile-advertising-2015-q2](https://operamediaworks.com/innovation-and-insights/state-of-mobile-advertising-2015-q2)
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [2015年十月5日 18:39 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/74 "2015-10-05T18:39:47Z")
Did anyone try “[Chrome custom tabs](http://blog.chromium.org/2015/09/chrome-custom-tabs-smooth-transition_2.html)” yet? Hopefully they’ll get some more attention with the introduction of Android 6.0 “Marshmallow” (they are backwards compatible with 4.x and up though).
[https://github.com/GoogleChrome/custom-tabs-client](https://github.com/GoogleChrome/custom-tabs-client)
This could be a very appealing workaround to [Discourse’s “JavaScript on Android” performance woes](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889). No, it doesn’t attack the heart of the matter, but it could do wonders for that 90% of your browsing time spent consuming your five favorite sites that you can actually be bothered to install a dedicated app for.
Combined with [ServiceWorkers](https://meta.discourse.org/t/exploring-serviceworkers-for-discourse/32422), the distinction between a custom chrome tab app and a native app would be fadingly slim.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2016年九月20日 07:59 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/75 "2016-09-20T07:59:23Z")
Closing this in favor of
> [@Beta testing the Android mobile app](https://meta.discourse.org/t/beta-testing-the-android-mobile-app/50165):
>
> We have been testing [our iOS app](https://meta.discourse.org/t/beta-testing-the-ios-mobile-app/49662) for a few weeks with great success and are happy to open up Android for beta testing! I am going to keep a list of known issues updated in this post, so be sure to check the first post in this topic prior to reporting stuff. How it works and what it does. The Android app is an open source react native application. The vast majority of the code is shared between our iOS app and it. Source code lives at: [GitHub - discourse/DiscourseMobile: Discourse Mob…](https://github.com/discourse/discoursemobile)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2016年九月20日 07:59 UTC](https://meta.discourse.org/t/discourse-as-android-application/22919/76 "2016-09-20T07:59:31Z")
[上一頁](https://meta.discourse.org/t/discourse-as-android-application/22919.md?page=3)