Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8813125
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T03:46:00+00:00 2026-06-14T03:46:00+00:00

We have a near complete application, and are trying to squeeze under the 50MB

  • 0

We have a near complete application, and are trying to squeeze under the 50MB download limit for Google Play.

When inspecting our APK to try to find ways to drop our file size, I noticed the lib\x86, lib\armeabi, and lib\armeabi-v7a directories that are described here. They correspond to the ‘Supported architecture’ option in project options of a Mono for Android project.

If I remove x86, I save around 1.1 MB on our APK size. (This is almost enough to get us under 50MB)

  • What are the drawbacks for removing x86?
  • Will my APK still run on x86 devices?
  • Is there any substantial market share on Google Play for x86 devices?
  • If it will not work on x86, will Google Play prevent my APK from being installed on x86 devices?
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T03:46:01+00:00Added an answer on June 14, 2026 at 3:46 am

    Note that the following answers are for general Android development and do not reflect anything specific to Mono:

    What are the drawbacks for removing x86?

    Your app will not run on x86 devices. Intel may cry.

    Will my APK still run on x86 devices?

    No.

    Is there any substantial market share on Google Play for x86 devices?

    IMHO, not presently. A few handsets were released in 2012 that are Intel-powered (e.g., Motorola RAZR i), and the first generation of Google TV devices were powered by Intel CPUs. But Google TV has switched to ARM, and it will be some time before Intel CPUs make up a substantial portion of the Android device ecosystem (again IMHO).

    If it will not work on x86, will Google Play prevent my APK from being installed on x86 devices?

    It should. If not, the Play Store has serious issues. While I have a RAZR i sitting here, I don’t off the top of my head know an app that uses native code that does not ship with x86, to see if the app in question is indeed filtered out of the Play Store.

    are trying to squeeze under the 50MB download limit for Google Play

    If a 1.1MB savings “is almost enough to get [you] under 50MB”, you are already in trouble. Apps tend to grow, not shrink, over time. If you expect that you will be able to switch to some other distribution architecture (e.g., use APK expansion files) eventually and just need a short-term stop-gap solution, cutting x86 may be OK. But you really need to have a plan for dealing with app size growth that takes you back over the 50MB barrier, and you may be better served addressing that now rather than shipping something and finding yourself painted into a corner as a result.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Here is my current situation; I am a near complete regexp illiterate, and have
I have implemented MGTwitterEngine in my application and it works near to perfect. The
I have near about 255 image frames for background animation, 99 frames of enemy
I have a table on near the bottom of the page, which I want
I have a text field that is near the bottom of the screen. When
I have a webservice that returns a list of Clinics near a certain lat/long.
I have about 40 workbooks with 1000+ columns and near 1 million records. Unfortunately,
In the near future, my organisation will have to change both the machine name
Python list comprehensions are nice, but near impossible to debug. You guys have any
I have a web application on a site that takes a while (~10 seconds)

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.