- May 18, 2007
- 23,878
- 5,317
- 108,890
[citation][nom]blazorthon[/nom]The statement in bold is exactly what I was talking about! My whole point was that the other companies should be fully compatible with Android if they're going to make devices and call them Androids or such. Running most is not good enough.I know from experience that not all manufacturers and such do a decent job when the responsibility is handed over to them.[/citation]
Many broken apps are broken due to hard-coded device feature expectations or simply poor app design, not due to any hardware, firmware, driver or runtime problems. Some apps are broken due to using the NDK, which is to be expected since the NDK is generally considered non-portable and Google strongly recommends AGAINST using it.
One example of apps breaking for silly entirely-the-app-developers'-fault reasons: when the N7 came out, most camera apps refused to launch, crashed or weren't available on Google Play because they required a rear camera while the N7 only has a front camera. This isn't a hardware or firmware problem, it is the app developers assuming every Android device has a rear camera.
Many broken apps are broken due to hard-coded device feature expectations or simply poor app design, not due to any hardware, firmware, driver or runtime problems. Some apps are broken due to using the NDK, which is to be expected since the NDK is generally considered non-portable and Google strongly recommends AGAINST using it.
One example of apps breaking for silly entirely-the-app-developers'-fault reasons: when the N7 came out, most camera apps refused to launch, crashed or weren't available on Google Play because they required a rear camera while the N7 only has a front camera. This isn't a hardware or firmware problem, it is the app developers assuming every Android device has a rear camera.
Facebook
Twitter
Instagram