If you’ve ever created a website or simply managed one, you’ll very likely be familiar with WordPress. They’ve made creating websites simple enough that pretty much anyone can do it. But as we move into the next generation of the internet, what about apps?
Websites are getting “old school”
Increasingly your customers, partners and employees are accessing the internet through an app on their phone rather than through a traditional website. Why? Rather than searching through billions of pages, they get targeted content, immediate access to services and perhaps most importantly – enriched functionality that allows them to be more productive. It’s a far more focused experience. But also, these apps don’t need to be connected all the time like a website – they can work offline and online. They’re connected when they need to be, but they don’t need to be connected to work.
Creating apps is way harder than websites
The internet is changing from websites to apps. Though there’s a big problem. The problem is that delivering an app these days is far more complicated than delivering a website. Whether you know it or not, the internet is going through a huge architectural shift in an effort to handle this paradigm change:
Server-side HTML to Client-side apps
Printing HTML documents to Cloud APIs
Server-side logic to Portable logic between device and cloud Browser to Native, Hybrid, HTML5
Desktop to Watches, Glass, thermostats, phones, tablets… and desktop
Guaranteed network connection to Transient connectivity
What does this mean for your business? Well yikes! Life got even harder and more expensive to get your new IT development projects shipped and out the door.
Where’s WordPress for apps?
Here at ManyWho, we like to think of ourselves as “the WordPress for apps“. Here are a few things you should be thinking about when you decide on your mobile strategy:
Mobile isn’t about one app
Just like a website is not about one web page. If you just have one web page, you don’t need WordPress – you can code that up in HTML just fine. Same with Mobile. If you just needed one app, code is just fine. But if you have lots of apps, it starts to “suck” pretty fast :0) Don’t make the mistake of thinking “mobile” is a fad and you can do everything in a single app.
Mobile isn’t just mobile
Remember those laptop users also. If you’ve been into a Starbucks recently (particularly in Silicon Valley), you’ll see a sea of laptops. Your apps need to work on every device. You mobile strategy should not be a mobile strategy, it should be a “cross-device” strategy.
Mobile isn’t a website
The mobile is so much more than a web browser. Be careful not to translate the world of laptops and desktops into the world or mobile devices. Network access is limited, people don’t do the same things on mobile as they do on laptops/desktops, the mobile device “knows” a lot more about the user than a desktop. Leverage the device to make people’s lives easier and engage more effectively.
Mobile is an architecture not a UI
Don’t be fooled into thinking mobile is simply a debate about HTML5 vs Hybrid vs Native. Mobile has triggered an architectural shift in computing that goes way beyond simple look-and-feel. It affects usability, security, distribution, support, management, etc.