Notes

• A popular open-source 4Chan Browser is Clover. I studied (parts of) its source code, which is pretty good by the way, and adapted parts of its code and concepts into Chanobol. By the way, I tried to do the same with Chanu and although I find Chanu as an app pretty good I didn't manage to get the project to compile and hade much trouble understanding its source code so that I gave up trying to understand it. PostView Design is inspired by Miko's (unpublished) 4Chan app.
• I took the code for e.g. image saving from Clover with minor adaptions. These adopted code parts feel a bit out of place which is not a big problem in itself. But if there is time or somebody wants to do it could good be adapted to better fit the rest of Chanobol's code.
• Chanobol has already been suspended once due to “explicit sexual content”. Even though I hid NSFW boards in the Play Store version by default it seems that the reviewer saw an explicit picture while browsing one of the safe boards (which I cannot control obviously). The new Play Store version simply has no boards by default which is a severe impairement to the discoverability aspect of Chanobol. You simply need to know the boards' short names beforehand and add them as favorites. This way, Chanobol's as sexually explicit as the Chrome browser itself—and the Chrome browser's still in the Play Store last I heard. I think this is an okay compromise as I believe most users of the app will already know their favorite boards and do not really use Chanobol to discover new ones.
• Chanobol has also been removed once from the Play Store. I received an e-mail from Google with the information that Chanobol violates the Copyright and Impersonation policies. Apparently, a lot of app developers received such removal mails due to Google's new enforcement approach. In short, these removal notices only contain very vague hints and so I had to be extra cautious to change everything about the app and the Play Store listing in order to not risk another suspension. That's the reason for the uglified logo with only three instead of four hearts for the Play Store version and the general thinness of the Play Store listing. I'm not happy about their policies but what can you do...
• In the beginning Chanobol used a fragment-based (navigation drawer) architecture as well as OkHTTP, Picasso and Retrofit. Over the course of development the architecture was switched to an activity-based (navigation drawer) architecture and Ion.
• I wonder, is there a possibility to catch a crash (NPE) in an activity and only finish the offending activity but not the others in the backstack? The ImageActivity sometimes crashes for out of memory reasons or because the image is just too big or because of deep zoom. But it would suffice if the ImageActivity simply would not open. There is no need to crash the entire app and force a restart...
• I sometimes get crash reports about problems I cannot realistically resolve from my end because they are caused by intricate problems in Ion or the Support Library or Satan Samsung bugs as a Google search often reveals.
• Crashlytics is godsend and essential. Without it I would not even have been aware of some very fatal edge case crashes/bugs...
• FYI: Basically, I wanted to create an optimized Chanu for myself with Chanobol. As I used only a subset of Chanu's functionality I actually did not really care about Chanobol gaining features beyond this subset like for example posting replies or choosable themes. My aim was and is to have a polished read-only 4Chan experience. The aim to implement more features (like posting) only solidified when users started to ask for it.