Are time-consuming custom fixes still commonly required in other (not camera reliant) Android apps too? I haven't really done any Android development since I had a Galaxy phone four years ago because this problem really turned me off to making hobby apps for Android.
Re:Introducing the new Snapchat
by tartuffe78 on Wednesday November 29, 2017 @12:50PM
(#15809041)
The camera & low-level video encoding / decoding are the most device-specific quirky in my experience. If you're making something that is just "software" it's all pretty standardized, but when you start accessing the "hardware" (video codec, camera, possibly low-level audio) is where the device specific differences catch you.
I have made countless cross-platform AR apps for mobile and desktop. Never an issue with WebRTC/getUserMedia, iOS, windows, etc. However Android is always a nasty problem. From incorrect aspect resolutions, image stretching, silent fails. Each device needs a custom fix which is time consuming and costly. No wonder why Snapchat went an alternative route.