Why it’s hard to find Android developers

Writing Help Online Chat

http://zoomia.pl/?dissertation-statistical-services-online Dissertation Statistical Services Online

http://www.sephiroth.it/?professional-business-plan-writers-in-cape-town Professional Business Plan Writers In Cape Town If you remove the huge number of “low end” (not profitable) devices from the Android share – as most people do – you’ll see why I said I can understand it.

Helping In Architecture Assignment Because you are not committed to Android development. You just think you “have” to do that. Because at some point you realize either that you need it to go global, or because a lot of users are asking it, or just because you think that porting your app will double your users overnight.

http://multiele.net/resume-writing-services-birmingham-al/ Resume Writing Services Birmingham Al

http://inet.edu.vn/upload/volunteer-homework-help-melbourne/ Volunteer Homework Help Melbourne

Well, try to think from a developer’s perspective. Android developers don’t find it very attractive to join a company where Android will be always the 2nd choice. That’s very frustrating.

  • Switch to Android (temporarily, if you want). Get to know the platform. Understand why some people prefer it. Read some articles about purchasing habits of the users. Understand the differences between ios and android. Etc.
  • Commit to Android as a platform. Talk openly at your company (and externally) about the market share, the benefits of the platform, and think about ways it can help your product – so that when an Android developer does join, he or she has some interesting projects to work on.
  • Offer a signing bonus to developers who switch to Android for your company.
  • Launch your next product on Android first (or at the same time as iOS).
  • Attend Android meetups. Speak at Android meetups! Encourage the developers you work with to do the same.
  • thisguy
  • Dan Nolan
  • Photis Patriotis

    I agree with the author that the big issue is startup mentality, but the problem is that is not going to change just because Android engineers want it to. A lot of companies big and small view iOS as their first foray into native apps for a lot of reasons that are really hard to combat effectively and there is not really a point in arguing here about.

    However, I think that the *way* porting is done could make a big difference. In my opinion, if you do it right, it shouldn’t be considered or feel like porting.

    I work at a mobile products agency (www.prolificinteractive.com) that does both iOS and Android, and of course, most of our clients want iOS first when they’re doing their first app.

    Our Android business, on the other hand is usually for clients with existing iOS apps. This is where it actually gets interesting, because our engineering team gets to learn about a whole new business, UI, and architecture, and we have an opportunity to consult on how to really make it work for Android. We even have designers do Android-specific designs and we pitch this as very important to clients because even though the branding and overall feel needs to be the same, the iOS experience is qualitatively different than the Android one.

    Is this porting? Barely.

    The Android eco-system is also a lot more receptive to open-source, and it allows for another avenue of interesting work for engineers.

    Again, my experience at an agency rather than a startup has made me realize that, as an engineer, it’s super hard changing the overall business objectives of a company (i.e. going Android-first instead of iOS-first). But, engineers and engineering leaders can make sure that the virtues of Android are pushed within the organization so their jobs are interesting and their products are appreciated by users.

    • Andy Bakun

      The “branding” argument never made much sense to me. A value of brand things consistently is in order to remind people of you where ever and when ever they are exposed to you. Yet there is a push to make IOS apps have the look and feel of IOS in-general, which is good from a UX consistency standpoint. But this isn’t branding your brand, it’s branding Apple’s brand. Additionally, the number of people who switch between using IOS and Android regularly *and* use the same app on both platform is *extremely* rare, rare enough to be non-existent. So similarity of branding between the different platform apps is meaningless.

      • Photis Patriotis

        I meant branding in the the first sense of it. The value of a company hiring us to build their mobile product is that it is unique and specific to their brand / products. If we were just building iOS apps that looked & worked like every other iOS app, you’re missing a big opportunity to impact your user-base.

        Using Material Design is the same principal. It is just a set of guidelines for how to have Android users understand and navigate easily. This is, again, added value for redesigning apps when “porting”.

        I don’t think it’s a good idea to build a product that doesn’t have a strong brand on its own and is not above and beyond the guidelines. If you care about your brand, it should transcend platforms. It’s not about making the experience the same on Android as iOS, it’s about how you want your users (in any platform) to interface with your company.

        • Andy Bakun

          Of course; we’re in agreement. There’s nothing that says that the experience needs to be the same on both platforms in order to be branded to/for the experience you want the users to have when interfacing with the company. But when doing a “port” is requested, the goal often seems to be to reuse as much of the work/research done for the first platform when creating it on the second platform, and this often falls flat. How your agency approaches creating the branding experience on a new platform looks like a better way to do it — but I’m sure that’s more expensive than a plain “port” when someone just wants to get something out the door to have checkboxes next to the list of mobile platforms they support.

  • Pingback: This Vicious Job Cycle Explains Why Startups Don't Use Android Even Though It's 80% Of The Market (AAPL, GOOG) | News()

  • Pingback: This Vicious Job Cycle Explains Why Startups Don’t Use Android Even Though It’s 80% Of The Market (AAPL, GOOG) | Whitelabel News()

  • Pingback: This Vicious Job Cycle Explains Why Startups Don’t Use Android Even Though It’s 80% Of The Market - AndroTab- AndroTab()

  • s73v3r

    No, you were banned because you were a fucking idiot, plain and simple. You were given multiple warnings, and you kept burying your head in the sand.

    • fbl

      You mean that ripping off the identity and content of several youtube channels was a bad idea ?
      I would have never guessed !
      It is an outrage that this guy got banned.
      I seriously wonder if this guy is not in fact a troll, such a blind naivety seems impossible.

    • Lono

      If 3 strikes policy is applied to the Internet, Google would have been banned long time ago by
      ICANN.

  • Pingback: This Vicious Job Cycle Explains Why Startups Don't Use Android Even Though It's 80% Of The Market (AAPL, GOOG) | Tech Auntie()

  • Anshul

    I am an Android dev. Our company has a trading app(IG) in ios and Android both. And believe me the

    Android app is rock solid and performs well.I disagree with the author but i believe its not hard find the Android dev but skilled Android dev.Some people’ s comment i read was The IDE is not good i would recommend use Android studio with all the google’s recommended tools you would love to be an Android dev.

    • tard

      You are an indian. Your opinion is irrelevant.

    • I believe Android is equally as good as iOS, or even more. But I don’t like the IDE, even Android Studio which uses Gradle for building. For even the smallest changes, gradle takes about 2 – 3 minutes to build and it drives me crazy.

  • America

    When you develop for Android, you’re developing for China and India. Moreover, you’re supporting China and India because one walk through Google’s office will reveal how many Chinese and Indians they hire over qualified Americans to build their Google products, which include Android.
    iOS is American. It’s used by Americans. It was made by Americans. I’m tired of these Obama-care touting liberal vegan pro-immigration H1B supporting activists arguing for the case of Android.

  • Derek Stutsman

    I disagree. I think porting apps is fun! Porting is a best case scenario, even – it’s a from-scratch app but with 100% known requirements!

    The real reason people don’t want to code for Android is the tools are terrible, and there’s no money in their app store. These two factors combine to make it unappealing to learn on your own time.

  • V900

    Actually, desirable mobile users worldwide ALSO tend to be iOS users. Desirable as in: Is willing and able to use online services and spend money on them.

    Sure, 100$ Android devices might have
    a larger share of the market, but look at the usage statistics for first world countries: Europe, Japan etc. The rates of iOS users are similar to the US: 30-50%.

    In countries like China and India, the affluent users are also for the most part iOS users.

  • Lono

    80% people in Taiwan use Android, but most app downloads comes from iOS. Market share doesn’t imply download share.

  • Pingback: This Vicious Job Cycle Explains Why Startups Don't Use Android Even Though It's 80% Of The Market - AndroTab- AndroTab()

  • Most of your observations about the lack of commitment and focus on Android are damn right.

    I’ve been in the position of developing iOS-first and then having to look for Android developers: one might think is hard to find iOS developers but it’s actually harder to find good Android ones.

    Up until now all I though about was that lower barriers to join Android development (it costs less to join the development program, and there are a lot of Java developers around the world) created a lot of shallow involvement from a technical standpoint. For iOS development you have to learn quite an hostile language and platform from scratch (Objective-C then, and now you have to deal with Swift, and, oh, the provisioning portal), and then you have to pay a lot more to join the program: all of this creates a way higher barrier and then a much more serious involvement.

    It’s harder to find good Android developers because most of them just “play around” with the SDK and maybe pull off some crappy apps just because it’s easier to do so for Android — so it’s lack of commitment from developers’ side, which may be hugely related with the lack of commitment on companies’ side that you are highlighting, but in my opinion the lower barrier is a strong feature of the Android ecosystem that negatively influences both companies and developers alike.

  • Ege

    This is a lame outcry, in my opinion, no offense

  • nuthinking

    As you briefly say, startups don’t do Android first because they don’t have time. First step for startups is to create an MVP (Minimum Viable Product) to evaluate the idea. Until this is faster/cheaper to do on iOS, less devices to test or design for, Android will be the second choice for startups.

  • Pingback: Android 2nd Choice - bosslee.co()

  • Джек

    Hey, I’m awesome android developer! I would like to work at NY, but… I live in Russia. ;(

  • Pingback: ¿Por qué es difícil encontrar desarrolladores especializados en Android? | Fravala.com - Las noticias de tecnología a tu alcance.()

  • Pingback: Week 39 | import digest()

  • Luisfer Romero Calero

    Companies around there:

    I am an experienced and motivated Android developer. Just pay me well (decent salary and/or company benefits), offer me a nice team and work environment, and tell me why should I work for you. That means: is the Android app going to be meaningful, or just a second plate for iOS? Is the app going to be useful for the society, or just another Tinder / Facebook thing? Am I going to enjoy the process of creating it?

    I think I am not stuck-up by asking these questions, but my experience tells me that this is very important even before starting working somewhere. I guess, that’s why it’s hard to find Android developers. We kind of “smell” some red flags before joining a project / company.

  • Yuanchen Deng

    Hi,I am an Android dev come from China.Our company has an app just called “impi”,which focus on chat based pictures.Now,we’d read you code of HorizontalVariableListView,it’s pretty good! But,we even have several problems about the effect of horizontal slide:

    We slide pictures as quickly as possible,the pictures scroll to a certain speed, when the time to stop scrolling,we need an effect of smooth stop and the current picture is in the middle(just like the app on IOS:Pixotale), at the present of this project, the picture is not in the middle.

    Now,we developers have no ways to solve this problems.Can you help with us? Anyway,if you provide a demo for us for the better.
    You may contact us with the e-mail below:

    dyuanchen@gmail.com

    Thanks!