Native apps are difficult to build and maintain Want to add a feature, change some part of the UI, change the colors, or fix a bug ? You can code as quickly as you want. But then you have to wait. Apple typically takes two weeks to approve any change to the code base. And till then your readers can’t see it. In those two weeks, they are usually pounding you on the App store with reviews and one star ratings. Reviews in app store are the single most corrosive thing that can happen to an app. 50% of the time user complaints are right, in which case, you are scrambling to fix problems, while the negative ratings pile up. And the other 50% of the time they are wrong — yet you are forced to change direction to stop the user venom. Google’s Android platform is better because of no approvals but Android users hate paying for anything there and its users are less into news apps than those on Apple’s App store. Developing for apps is also different than developing for a browser because connectivity changes all the time. The dreaded “low connectivity” when the device thinks is trying hard to reach the network but can’t means for your reader clicking around in the app — images won’t load, articles won’t pull up. And to get around that you have to build a robust caching experience, focus on performance — initialization and load times, and have good error messaging (nothing is more frustrating in an app than a white screen where you can’t understand why something is not showing up.) If you don’t have the engineering resources to do all this, why not instead focus on the mobile web?