Tag: Mobile App Backend

The top five tips for recruiting app developers

Congratulations! Through hard work and too many all-nighters, you and your small app development team have managed to start turning a real profit. You can see your small company already rising through the ranks of competitors – and then someone tells you that you need to expand your team if you want to keep rising. In order to deliver your next project, you’re going to need to start recruiting app developers to get things done on time. Remember it’s only natural that as your app development business income grows, so too will your costs and hopefully you’re retainable profit.

It’s one thing starting out with friends when you start out after university. But when it comes to the real world and developing apps for paying customers, it becomes less about camaraderie and more to do with cold, hard execution. You’re going to need people you can trust, people who are hardworking, dedicated to the cause, highly motivated, creative and have the ability to do the job you need. Chances are if you’re a small app development studio, you’re not going to have a huge amount of time for training. In actual fact, spending your time trying to teach noobs app development can be counter-productive, if it’s keeping you from doing the important stuff in the business. You need people you can trust to do the job and learn the ropes quickly.

Nobody will tell you when it’s time to scale up and add more staff. This is something you need to work out for yourself and you have to be able to judge the warning signs. Similarly, you have to be able to judge if the person you’ve hired is a winner or a turkey. Again, you have to do this quickly before said individual is capable of doing more harm than good.

Well, having gone through the growing pains of being a small start-up ourselves, Kumulos  thought we could lay out just why recruitment is so important, and a few tips on how to nab yourself that next app dev superstar.

Why recruit?

It seems like a question with an obvious answer, but when looked at a little closer it’s a bit more complicated than just expansion. If your project is late, over budget or your customer is screaming down the phone for answers, chances are you’re under-resourced and under-delivering. You should plan your recruitment at the start of any project. You need to develop a scope of work, a timeline to complete the project and make some assumptions about the resources required. This should take the form of a resource plan, and whilst they are assumptions, you need to be as accurate as possible in determining your overall resource requirements to complete the project. Take the project as a whole and subdivide the overall scope into a series of manageable milestones and delivery dates. This will help to inform your timeline for completion. You can then work out based on your current level of resource who can do what and identify any potential gaps in the project team. Where there are gaps, you have to fill them and there are a number of ways you can do this.

If you’re a small app dev team, it’s likely that you’ll have had the same team for a while. You’ll have worked on a couple of projects together and there will be a real “gang-hut” mentality going on. You know each other’s working habits, strengths and weaknesses and probably also what happens when everyone has too much to drink. The idea of bringing someone in, regardless of whether you actually need them or not, can feel like adopting a stranger into a family; that they’ll somehow disrupt your gang’s dynamic and work flow.

The first thing that you need to do is shake this mindset completely. If you follow our tips and find a great dev to add to the team, all you’re going to get is a bigger and better gang than before. On a business and project level, if your team is lacking a certain set of programming skills, or they’re just too stretched to take on any more work, having another person, or people, around to plug those gaps makes sense.

Also on the business side, as we said before, the base answer for recruiting is usually to expand. Maybe you want to develop two apps side by side, or you’re starting to take commissions from clients. Either way, you’re team is just not big enough to keep all those plates spinning, and you’ll need more people to spin more plates.

Whatever the reason for recruiting, the most important thing to bear in mind that you should always be trying to find the absolute best person that you can find for the job. Ideally that means you want someone who knows their stuff, has experience working within the app industry and will also fit right in with your team. By finding someone like this, you can only improve your development work, and by extension, your profits.

So how do you go about finding that “superstar”?

1. Know what you’re looking for and what you want out of them

It’s always better to be prepared, and with developer recruitment it’s no different. Take some time before you start to advertise the position to work out exactly what their job will entail. On the surface you’re looking for an app developer yes, but do your apps frequently need knowledge of other programming areas? What about your general work environment? If you’re a small developer you and your team may be “doing a bit of everything” and always able to jump into someone else’s work, so also take into account flexibility and ability to learn new things.

As Joel Spolnsky over at joelonsoftware.com says, ultimately you’re looking for someone who
“[is] Smart, and gets things done.”

So always bear that in mind before you start your search. You are looking for a good app developer who is going to fit into your workplace. That means that you have to be willing to go the extra mile, but it’ll be worth it in the end.

2. Know where to look for developers

This is a mistake many businesses make, even large and established ones. Instead of targeting their job adverts for developers to places good developers will see it, they put it up on places like Craigslist and then wonder why they are inundated with CVs from people who don’t even know what an app development kit is, let alone what to do with it.

As a small developer, or even if you’re larger, you don’t want to be trawling through hundreds of CVs to find the diamond in the rough. It’s a waste of your time and it’s definitely not the most efficient way to go about finding your developer.

Instead target places that app developers are going to be. Attend app development and technology conventions, especially if they’re related to the kind of apps or technology you’re working with. The devs that are attending there are much more likely to already know about and be familiar with a similar environment that you’re working with.

When San Francisco based Getaround was first getting off the ground, co-founders Sam Zaid and Jessica Scorpio found their superstar developer at a convention and never looked back. Never underestimate the power aggressive networking in the correct environment.

Outside of that, and for more general job advert placement, ask yourself, if you as an app developer were looking for work, where would you go? Would you go to websites like Monster where every add has a thousand applicants? Or would you look for something more specific? Go to websites and forums where app developers come together to talk shop, target tech specific job boards and make sure to advertise clearly on your own website as well.

3. Whittle it down

Even when you’ve found a group of potential hires, you know that you only have room for one. So it’s time to start cutting away people from the total.

Obviously, this depends entirely on how you’ve gone about your recruitment and how you have arrived with your potential candidates. If, like GetAround, you’ve found a group of developers at a convention, continuing to follow their example is not a bad idea. Zaid and Scorpio used a series of 2 minute interviews to cut the initial numbers down, and then with their final choices they presented them with an unpaid “prototyping” challenge which essentially asked the app developers to create a mock-up of their app-in-the-making. In the end they settled on one dev who’s results they liked so much they made them technological director.

The same finalisation process of presenting your applicants with an app development challenge can be used in more traditional settings, but first you’re going to have to get through the initial stages.

If you have a mountain of CVs, you’re going to have to get really harsh with your elimination process. First, and easiest, get rid of anyone with no programming and especially no app development background (there will be more of these than you’d think possible). Next up it starts to become more of a personal game, but targeting things like good English makes sense. If someone has barely understandable English on their CV, what makes you think that their ability to communicate effectively with you and your team is going to be any better? The same can be said of untidy and terribly formatted CVs, it shows laziness and a disorganised mind, two things you don’t want to bring to your team.

Every business goes about sorting CVs slightly differently, but if you keeping bearing in mind exactly what you want from your potential hire then you’ll likely find it easier than you think. Always remember, if you’re not sure, it’s safer to decide to put a CV in the “no” pile. All you’re doing is saving yourself time later.

As for interviews, again it comes down to what exactly it is that you’re looking for from your new team member, and there are whole series of books written on interview techniques, so we won’t go too in depth here. It helps if you have a plan of how you’re going to interview someone before you start, and it’s even better if you tailor it to their CV. Being able to ask a developer about their background is a quick way to gauge whether they are engaged and interested in app development, which is a good sign. No one wants to work with a passionless developer.

4. Remember to make your job the best job

This is something that, again, many businesses fail on. As you’re the one who’s put up the ad, you feel like you are the one who can make all the demands. But remember, a good app developer is always going to be in demand, and they’re likely to know it. That’s not to say that they’ll be making outrageous demands (although some may well do that), it’s just to remind you that the best talent, the ones that you want for your team, are likely to have a few offers waiting for them. So make sure to sell your app studio, your team, your apps and your vision for the future to them. Let them see that you are just as passionate about this work as they are and that if they work for you, they’ll be working with people who they share common ground with and can respect.
It’s no guarantee, but it certainly helps when you’re fishing for the best talent, which is exactly what you should be doing.

5. Knowing the ropes

Ultimately, recruitment is an art in and of itself. Large companies have entire departments dedicated to it, or even outsource the job to agencies who’s only goal is to find the best and brightest talent. There are libraries of books written about it, and yet plenty of businesses still don’t manage to find the people they are looking for.

When you’re looking for your next superstar, always remember that ultimately, this person is going to become part of your development family; and if you want them and your current family to be happy, it’s always better to take your time and make sure you’ve got just the right person for the job.

App Backend Design (Part 2 of 3)


The App Build feature in Kumulos is a mobile Backend-as-a-Service (BaaS) on which you can very easily and quickly build and host your App Backend. App Build provides secure, scalable SQL based data storage in the cloud that can then be accessed and manipulated via a REST API and/or RPC API methods from one of our many client SDKs including iOS, Android, PHP, Windows, OSX and more. This leaves you free to focus on building the rich UI and UX that your clients crave, without having to worry about the hosting and availability of your app backend.

In part 1, we looked at how to design the relational data model for your app backend with Kumulos. Now, in part 2, we’re going to use these example data models to implement your app backend in Kumulos, showing how this then allows related data to be retrieved from a single API method.

Implementing one-to-many relationships in Kumulos

In part 1, we used the example of a mobile application that allowed users to upload and share photos to illustrate how the one-to-many relationship can be used to model related data. We also showed how this relationship can be implemented using a Belongs To field. We’re now going to look in detail at how to implement this data model for your app backend.

First off, we need to add a table to store a user’s name and the date of their birthday.

app backend users table

Next up, we need to create a photos table, containing a data field for the photo data, a title and a description.

app backend photos table

A photo has a photographer who took the photo, and any given user has a collection of photos. The Belongs To field is used to express the one-to-many relationship as follows:

This record belongs to ‘Users’ as (their) ‘photos’. This record has a ‘photographer’.

When a user is deleted, any photos that they’ve taken will also be deleted.

We can extend our data model further and introduce the ability for users to comment on photos. To do this, we need to add a comments table to store comments on photographs.

app backend comments table

This table used two Belongs To fields to implement two one-to-many relationships. First, we say that the comment has an associated photo, and the photo has a collection of comments.

Next, we say that the comment also has a creator (a user who posted it) and therefore each user has a collection of posted comments.

Because a comment belongs to both a user and a photograph, when either the owning user or photo are deleted, the comment will also be deleted.

“postedComments” is used instead of “commentsPosted” because Kumulos determines the relationship type from whether or not the word in the “as” section is singular or plural. So, you must use phrases ending with either a plural (for one-to-many relationships) or singular (for one-to-one relationships) noun.

Implementing many-to-many relationships in Kumulos

In part 1, we used the example of a mobile application that allowed users to share their favourite meals to illustrate how a many-to-many relationship can be created using  two one-to-many relationships. Lets look in more detail at how to implement such a data model for your app backend.

Lets add a table to store information about people. Essentially we want to know their name and why they like food.

app backend people table

We’ll now add another simple table storing a title, description, and the name of a chef who is famous for the meal.

app backend meals table

Now, here’s where the magic of this data model happens. We add a favorite meals table to store the link between a person and a meal. It also stores what the person likes most about the meal.

app backend favorite meals table

The many-to-many relationship between people and meals has been captured by these two one-to-many relationships:

  1. One person has many favorite meals (through connoisseur)
  2. One meal is the favorite dish of many connoisseurs

So, to select a person’s favorite meals, you should select from favorite meals (including the meal record) and filter the select by the person’s ID. Similarly if you want to know who likes a particular meal, select from the favorite meals table (including the connoisseur) and filter by the meal ID.

Because a favorite meal belongs to both a person and a meal, if you delete a person then the entries for their favorites will be deleted but the meal itself wont. The same is true if you delete a meal. Any people who like that meal will stay put but any trace of them ever liking it will disappear.

Fetching related data from your app backend

Having added Belongs To fields above to implement the one-to-many and many-to-many relationships in your app backend, you can now exploit these relationships to fetch related data from your app backend with a single API method. When you create a new API method with a select action, the API editor will allow you to include records linked by “Belongs To” in your result from select actions.

Using our mobile application for sharing photos as an example, we can add a new API method on the photos table.

app backend create api method

Then, we can check the comments box to say that we want the related row(s) from the comments table returned with each row from the photos table. Neat huh!

app backend return related data

In Part 3, we will look at how we can go a step further and filter the data you fetch from or update in your app backend based on the data it is related to. But again, if you cannot wait until then, further information can be found in the docs.

iPad App failure grounds American Airlines – Really!


I read this and my first reaction (probably a bit like yours) was…Huh?

An iPad App grounds an Airline? What’s a mobile App doing as part of an airlines critical business systems?

Dig further and it gets interesting. It makes sound business sense for AA (and others) to use mobile technology. Here its a $1.2m in savings a year – through weight reduction. I did notice on recent travels that you rarely see aircrews lugging those huge pilot cases any more – and this is why. Its all gone into Apps; light, flexible easy to use. It shows just how central mobile app technology is. Some smart people say that we are just at the start of this revolution, and errors like this show the technology has a way to go to fully mature. What it makes clear is the big business impact that a simple App crash can have even on even the most trad of businesses.

(OK, so maybe impact and crash aren’t the best words to use here) – But you get my drift.

What happened and why shouldn’t it have happened

OK, so hindsight is great,  isn’t it? Makes us all feel really smart. But it has to be said that you’d really think airline IT boffin somewhere would have thought this through and done a risk assessment.

So it appears that the App (called FliteDeck – made by Boeing business Jeppesen) crashed when it tried to access charts stored in a back-end database. Somehow the DB had duplicate files that the App couldnt resolve so errored and crashed. The App was used to manage the fight plan, no flight plan = no flight.  The only way to fix it was to connect to Wi-Fi and reinstall the app. I’m guessing it’s probably not that easy at 35,000 ft.

This did make us Kumulites scratch our heads and think though. It shows again how important back-end infrastructure is when Apps are critical business tools. If they had been using a mobile back-end as a service like our mBaaS and running kScripts to check for file duplication in the database, then this just wouldn’t have happened. Even better would be to ensure they are using hook-ups to pull data from other (reliable, tested and trusted) sources rather than replicating sources, because that’s how mistakes get made, isn’t it.

There’s a lot of chat in Kumulos HQ about this. The conclusion is what happened here was a good thing (because no one got hurt) and may jolt techs to realise that a 4 tier architecture with a mBaaS (with kScripts and hookups)  as a consolidation layer is the way to go.

Enterprise mobility and utility Apps are here and here to stay but right now the DIY back-ends still feels a bit flabby – firm back-ends run by those who know their stuff is the future.

The Unstoppable Rise of Backend as a Service (BaaS)


For any of you skeptics doubting the commercial feasibility of Backend as a Service (BaaS), you should check out Facebook’s acquisition of Parse for a rumoured $85 million (And then the subsequent fallout in 2017). The acquisition enables Facebook to provide their own proprietary backend solution for app and game developers. The integration between Facebook and Parse will enable the social networking company to provide a superior user experience through enhanced responsiveness and reduced latency.

Parse has been described as BaaS (backend as a service) and XaaS (everything as a service). If you’re an app developer, this means you can focus on the front-end design and development of your apps and games, without having to worry about setting up a server. This can enable app developers to manage messages between users, push notifications and storage of apps and games.

Kumulos is neatly listed as a BaaS provider on both Wikipedia (http://en.wikipedia.org/wiki/Backend_as_a_service) and the Developer Economics website (http://www.developereconomics.com/sector/baas/). These various BaaS platforms have been emerging now for nearly 7 years and here at Kumulos we’re proud to say we were one of the first. Kumulos was actually launched before the term ‘backend as a service’ had ever been created.

Find out more about mBaaS and Kumulos here.

Pavlov Poke: The painful way to wean yourself off Facebook


Are you a Facebook addict? If you’re online, it’s at least probable that you check it once a day, probably more like multiple times a day. Do you even know how much time you waste on it? Probably not, but it’s a good bet that it’s way more than you think, or would be comfortable with. Afterall, just exactly what are you doing there? Unless you’re actively talking to someone, is not the case that you’re essentially people watching, but online, on your own?

 This video is food for thought.

Anyways, two P.H.D.s at MIT tallied up how many hours a week between them they were wasting on FB a week. Turns out, a lot. How much is a lot? 50 hours. 25 hours hours a week they were wasting each. That’s a part time job right there, just on Facebook. They realise they had to do something, but what?

Well that’s where the Pavlov Poke comes in.

They hooked up a metal plate to their keyboards that, every time they went on Facebook, would give them a painful (but not dangerous) electric shock. It’s essentially aversion therapy 101, and it’s a hilarious way to go about trying to aid your productivity. We all could probably use that for our own keyboards; even if we’re not Facebook users. We’ve all got our little vices online, websites that we sink hours into because they give us our daily hits of information. Imagine how much more we could get done if we weren’t always alt-tabbing out of whatever we’re supposed to be doing in order to watch stupid videos of animals failing or to follow a link train and end up reading up about how Taylor Swift only wants to be in a relationship to get new material to write about (seriously, this happened and that is true, look it up).

A little aversion therapy may go some way to curing us of our crippling need to read that one little bit more information. Or just make our offices really funny.

Whatever the case, Kumulos is here to provide you with a non-addictive but oh-so-useful Mobile Backend as a Service to cure your app development woes. So get in touch today, if you can tear yourself away from Facebook long enough that is.


Amazon.com goes down as well, not to be alarmist but…


Almost seems like there’s a pattern here doesn’t there?

In the last week; Facebook’s ban bot went mental and kicked a whole bunch of users, Google went down for a few minutes and took 40% of the internet with it, and finally Amazon.com went down for half an hour yesterday, dragging the Canadian site down with it.

Then there’s the fact that the NYT went down, and CNN and the Washington Post were hacked.

All these big bastions of the internet seems to be dropping like flies right now, and although paranoia is what the internet does best, it seems interesting to the casually observant eye that all of these big services have suffered glitches so close together.

“It’s very unusual to see such a number of high-profile websites all suffering peak-time outages within the course of a few days of each other,” said Chris Green, principal technology analyst at the Davies Murphy Group consultancy.

“People are going to be very interested to know exactly what the reasons were for the incidents that are still unexplained because the implications are huge: we’ve seen everything from users being unable to see their email to visitors and third-party retailers who use Amazon’s marketplace being unable to buy and sell goods – all happening seemingly with no warning.”

(source: BBC news)

So what are the explanations?

Hacking groups getting uppity? China or Iranian military trying to steal some more data? Could it be Skynet flexing its online muscles for the coming apocalypse?

Let’s hope it’s not the latter.

What’s interesting is that there’s been no press release from the major companies stating the causes of these faults. We shall have to see.

Until we find out, you can rely on Kumulos’s Mobile Backend as a Service to be reliable, and not associated with any apocalyptic machines. Promise. So why not get in touch?

You’re doing it wrong LG


Marketing is tricky, we all get that. In this all connected world, where we know what everyone is doing, all the time, it’s difficult to stand out from the crowd. Which is why companies are turning to more and more… interesting ways to put their product out there. So, in that vein, LG decided the best way to attract attention was to tie 100 vouchers for a free, brand new, G2 to helium balloons and then tell people when and where they were releasing them.

The results were, in a word, predictable.

The crowds turned up with BB guns, knives tied to sticks and essentially any kind of weapon that was likely to bring down a balloon; and then they surged when the balloons were released resulting in 20 people being injured. LG have offered to cover all the medical bills of those injured and that they take “full responsibility” and that other events have been called off for “safety concerns”

You can see the reasoning behind LG’s idea. Get people hyped up about getting a new smartphone, and then gamify it so people don’t get all sore (no pun intended) when they don’t get the phone. But really, someone somewhere should have probably been able to predict that telling people they can get a £600 smartphone for free if they bring down a balloon with a voucher attached would result in a situation like this.

Of course, this event puts LG front and centre in the public eye, but it doesn’t paint LG in the best light. This is the really tricky thing about good marketing, attracting attention is not that difficult, but you want it to be the right kind of attention. The Russian tampon advert was good because it had a sense of humour, was edgy and turned heads. The Marmite ad linked earlier has got a lot of negative reactions from people claiming it to be trivialising the plight of real animal abuse cases and the people who deal with them and despite 400,000 views, has had no appreciable increase in sales.

LG will go home and lick their wounds and their next publicity stunt will probably be quite safe and tame, but it will be interesting to see what the ultimate fallout from this event will be for them.

Luckily, Kumulos won’t be asking you to chase balloons through the streets; we just offer a solid Mobile Backend as a Service that promises to make your app development life that much easier.


Internet popularity and gaming the system


In marketing these days, virility is everything. Why spend thousands on a TV advert that people are most likely to switch off of when you can make something catchy, post it online and bang, you’ve got hundreds of thousands of people talking about you and your company. Just look at Psy (remember him?); despite Gangnam Style seeming to be an accident, it really was nothing of the sort. Go back and watch the video with a neutral eye; it has all the hallmarks of an incredibly clever plan to hook people in.

It’s got a catchy tune, a singer that looks and sounds unique (to western audiences anyways), he’s doing all kinds of zany things that you instantly want to mention to your friends and, of course, there’s a dance that’s as silly as it is fun and easy to learn. Package all that up and you have one of the biggest cultural phenomenons of 2012.

There was no good reason not to share Gangnam Style, and as soon as the shares and the likes started coming, they carried on in a state of perpetual growth. This is the power of social proof at its finest.

Incidentally, Apple understand the power of social proof all too well. Their products are expensive, deliberately so. Sure, the build quality is solid, but that’s no reason to charge an extra $300 for a computer with, let’s face it, average specs for the price. It’s the same with the iPhone. Compare it to any flagship Android currently in terms of tech specs and it falls flat on its face; and yet iPhones are consistently more popular overall. Why is this? To those who value performance over pure aesthetics, it can be baffling; but it’s simple really. Apple is premium, Apple is expensive, and Apple is social proof that you only buy “the best”. It’s the same reason why people buy Sony products for their living room even though, objectively, they are no better than other big manufacturer’s efforts usually.

It’s all about proving yourself to be cool, in the end.

And if you’re trying to market online, this is something you need to tap into. Recent research by Sinan Aral has found that by posting a link that’s already supported by a few likes or other shares, he could artificially boost its popularity by up to 32%. This is supported by the idea that, generally, we want to share things that are positive and/or if they are negative, they’re funny about it. After all, no one wants to be seen as a constant downer.

So if you’re marketing your latest app, bear all this in mind, you never know what will become the latest viral sensation. And if you’re still developing your app and you need a Mobile Backend, look no further than Kumulos.

Why Window’s failings may be Google’s winnings


Google have always been ones to slip into any market that looks like its got some wiggle room. They did it with mobile, they did it with browsers, they’re doing it with wearable tech, and they’re also doing it in the PC market. That self same PC market that has been on the blink for years, shrinking and slowly spiralling down as Microsoft see their profits and margins go with it.

The result of this has of course been that Windows OEMs are getting twitchy. Acer has been seeing dropping profits recently, their Windows 8 tablets and computers really not doing well at all. So how can OEMs like Acer recover their loses?

Well, if Google has anything to say about it, it’ll be through Chromebook and Android.

Already Acer make the C7 Chromebook that sells for $199, riding on the back of the netbooks of old. Running Chrome OS, these Chromebooks aren’t the biggest players in the PC market by far, but they’re a strong indication of where things are headed. Acer are predicted to have some 12% of their revenue come from either Android or Chrome based devices by the end of the year, and Chromebooks alone are looking to be 3% of their sales. A small number perhaps, but when you take into account that these Chromebooks are essentially running experimental software and are largely cloud based in their storage, it’s quite an impressive number in such an entrenched market.

Windows 8 and especially Windows RT seem to be increasing the rate of the market move away from PC. ASUS have come right out and said that RT is killing their windows tablet sales, whereas the Nexus 7 is doing rather well for itself in comparison. If this becomes a trend, where Windows won’t sell but Android and Chrome will, Microsoft will be likely to see Mountain View take more and more of their customers.

Google have been very savvy in how they are managing their move into the PC market; by using OS that can all talk to each other across multiple different devices, we could easily see the day where your phone, tablet and laptop all sport the same OS and even the same homescreens as Google creates the “One account to rule them all” style mindset.

2013 has so far been the year of Android and Google, and as we approach fall, we can only wait and see if Apple can bring the magic and capture us all back from the little green robot.


The Moto X arrives! (but only in the US)


It seems like we’ve been hearing about the Moto X for ages. There have been rumours of Motorolla’s new phone kicking around online since mid-2012, with occasional design leaks and other info trickling out over the course of early 2013. That is until today, when it was finally unveiled to the world.

Sporting a 4.7inch 720p AMOLED screen with over 300ppi, a 10Mp camera with full HD recording, Android 4.2.2, 2Gb of RAM and a 1.7Ghz dual core processor it might not be the top in specs, but the Moto X is planning to make up for that. How? By allowing customers to fully customise the look and feel of their new phone as well as a host of advanced sensors collectively called X8 that allow the phone to know about its current environment and adjust accordingly, along with specialised language processors so voice commands work better than ever before.

As for the customisation, you can choose your back, front, and accent colours, the storage space and order any accessories you might want. The cases seem to come in a range of colours ranging from attractive to garish and everything inbetween. The phone is set for a probable release around the end of September, so we can all get excited about this new phone right?

I mean, it’s going to be released internationally right?



Turns out no, the Moto X is only getting a release in America currently, with “no current plans” to bring the phone to Europe.

“We are firmly committed to building a portfolio of products in Europe that show the best of Motorola as a Google company, but at this time don’t have any immediate plans for Moto X to come to the region,” Motorola said in a statement.

Well f*** you too Motorola.