Tablets, Phablets and Whether To Design for Larger Screens

IDC has some new research that shows that the tablet market has continued to contract due to competition from alternative devices…










What does this mean for developers? At first sight it might mean that it’s less viable to create tablet-specific apps or tablet-specific screens layouts. However, the IDC research suggests that “Cellular-enabled tablets are outgrowing the rest of the market”. Statistics from Flurry show that these devices, better known as phablets, tripled their share of active users over the last few months…


However, if you compare iOS and Android then the latter has by far the larger proportion of phablet users…











The large proportion (36%) of phablet users on Android suggests that particularly Android developers should still be considering how to make the most of larger screen sizes.

336 million Smartphones Shipped Worldwide in Q1 2015

IDC has new research showing 336.5 million smartphones were shipped worldwide in the first quarter of 2015. Samsung has overtaken Apple as the leading vendor.


There’s no mention of the mobile OS market share in this press release but, looking at the above graph, it’s likely to be relatively unchanged compared to previously.

Mobile Payments Whitepaper

The Application Developers Alliance have a free whitepaper on Mobile Payments (pdf) with an emphasis on the issues affecting merchants.


It offers a simple overview on the payments ecosystem and covers beacons, digital currencies, omnichannel, NFC and mobile wallets. It mentions issues such as security, fraud and market fragmentation.

You will Never Have Complete App Security

When I speak with clients, there always seems to be be the impression, on their part, that things are either secure or not secure. Unfortunately, whether it’s desktops, laptops, servers or smartphones, the principle is the same: You will never have complete application security.

It will always be possible to fool users into installing things or doing things they shouldn’t. There will always be vulnerabilities that allow root and hence allow, for example, memory dumps of decrypted data. There will probably always be NSA backdoors and the possibility to eavesdrop on radio frequency (RF) noise. There will always be some users that root their devices making things considerably easier for attackers.

This doesn’t mean you should give up and not consider security at all. For all apps, simple safeguards, for example, keeping data in the Android sandbox, provide basic protection with negligible extra effort. At the other end of the scale there’s a class of apps, for example banking and payment, that needs to make it algorithmically time consuming (via encryption) or extremely technically difficult (via tamper protection) for attackers to read sensitive data. You will never have complete application security but you can have high security that, for all normal intents and purposes, will keep your sensitive data safe.

Android App Hacking Getting Easier

appsecIn my post on my Thoughts on Google’s Android Security 2014 Year in Review  I mentioned that security isn’t only about potentially harmful applications (PHAs) being installed. It’s also about the ability to easily obtain information from stolen devices and reverse engineer apps.

Today I came across a tool from AppSec Labs, AppUse, that enables easy offline reverse engineering of apps. It brings some well-known command line tools, used to reverse engineer APKs, together with a hooked ROM to allow access to things (e.g. files, communication, database, encryption) you can’t normally see externally. This is all wrapped in an easy to use window UI. This tool will be mainly used for analysis of malware and penetration testing. However, it’s obviously also possible to use it for nefarious purposes.

If you have intellectual property within your app, think your app might be copied or your app needs to be particularly secure, (eg banking, payment, enterprise) you will want to look into obfuscation/packing and tamper detection.

Mobilegeddon WordPress Learnings

wordpressAbout a month ago I wrote about Mobilegeddon.  Changes coming April 21 2015 will result in mobile friendly sites being promoted more, by Google, when searches are from mobile devices.

At first I wasn’t going to do much about it. This site is ten years old and ran a ten year old version of WordPress, patched in places and some unused remote access functionality disabled as I had learnt of vulnerabilities. It used plugins, particularly one for ‘related links’ that I knew wouldn’t work with new version of WordPress. The heavily modified template would also have to be changed to a more modern mobile-responsive template. It all seemed like too much effort for something that isn’t my core work.

More recently I had some spare time so created a copied, separate site to try and attempt the upgrade to see how difficult it would really be. You can’t just upgrade from 1.5 to 4.1.1 and instead you have to upgrade the database in stages, each time for a few WordPress releases at a time. It took some time but was more straightforward than I expected. I ended up dropping the related links plugin I was using and started using a more recent one that dynamically creates the related links rather than me having to select fixed ones for each post. This also now has the advantage that old post’s related links now change, with time, as newer related posts are created. I have also been able to add the latest SEO plugins.

I am pleased with the result. It’s much easier to author posts now. Interestingly, Google is now indexing the whole of this site rather than less than half of the site previously. Presumably, the new template (or SEO plugin) is more Google bot friendly. The site is also now responsive and passes the Google mobile friendly tests. It took a lot less effort than I anticipated and if you are in a similar dilemma as to whether to upgrade I’d recommend you do so.


One affect I wasn’t expecting has been the huge increase in number of brute force attacks on the admin login page. I noticed this when I saw the WordPress login page getting of a factor of 100 more hits than all (the thousands of) pages on the rest of the site. There are many attackers, every hour, repeatedly trying to access the admin page. I can only think that going from WordPress 1.5 to 4.1.1 the site now looks more like a typical WordPress site than it did! I have since strengthened the login password and have added a lockout plugin that works after 4 failed attempts.

We will have to wait until the 21st April to see if the changes will have any affect on traffic.

Focus on Retention

mobileworldliveMobile World Live quotes some Gartner research into app use that says that ‘Developers need to focus on user retention as app market matures‘.

“App providers will need to focus their development, marketing and branding more intensely toward retention strategies”

Meanwhile, Localytics say ‘App User Engagement and Retention on the Rise‘. The average number of app launches per month is up 5% over the quarter. App stickiness improved in Q1 with engagement growing by 13% and retention by 41%.


Read the previous articles below to gain some insights into how to increase app retention.

Complexity Cost

firatroundreviewThere’s an interesting article at First Round Review by Kris Gale, VP Engineering at Yammer, on “The One Cost Engineers and Product Managers Don’t Consider”

“Complexity cost is the debt you accrue by complicating features or technology in order to solve problems”

or put another way…

“The work of implementing a feature initially is often a tiny fraction of the work to support that feature over the lifetime of a product”

People tend to ask how long a feature will take to implement but there’s rarely any consideration as to the long term cost.

I believe there’s even more to the problem than complexity cost. The long term cost is also related to how well the feature is implemented. It can sometimes be implemented more than one way with different longer term costs or put it another way, different technical debt.

For example, be wary of using/overloading old mechanisms to support concepts for which they obviously weren’t designed – this is usually a sure sign of adding technical debt and complexity cost. Instead, re-design so it’s clearer and simpler.

So, when thinking about estimates, try to also think about the complexity cost and technical debt.