Does the use of Google APIs limit Android device support?
<p>My company has an Enterprise client/server application that runs on Android.  I am adding a feature that will include a MapView.  I am trying to decide if I should use Google Maps or some other mapping service.</p>

<p>My concern with Google Maps is that it requires Google APIs.  These APIs appear to be included in all Google-approved versions of Android, but that may be too limiting for us.  We do not want one feature to limit the devices we can support.  I am particularly concerned about Amazon which might be moving away from Google Maps.   This might prevent us from running on the Kindle Fire.  </p>

<p>I have looked at OpenStreetMap, but the quality seems to be a notch or two below Google.</p>

<p>To summarize, I am looking for guidance on the following:</p>

<ol>
<li>Am I correct in thinking that Google APIs may limit the Android devices we can support?</li>
<li>Can I bundle the Google APIs with our Android application, thus ensuring that they are present on the device?  This is the model for other 3rd-party software.</li>
<li>Could anyone suggest a reasonable alternative to Google Maps?</li>
</ol>
