5 ms·
Yes. That's what a Camera Intent would do: https://developer.android.com/training/camera/camera-intents https://developer.android.com/training/camera/camera-in
by daveoc64 4y ago
Yes. That's what a Camera Intent would do:
https://developer.android.com/training/camera/camera-intents https://developer.android.com/training/camera/camera-intents
This is the "I want the default camera app to take the photo for me, and I just want my app to be given an image afterwards" approach.
- oblio 4y agoLet's hope Samsung (and all the other Android phone manufacturers) adopt this by 2050 :-)
- izacus 4y agoThey adopted this in 2009, what are you going on about?
- oblio 4y agoI've just checked on my phone. Telegram, WhatsApp, Signal, Google Messages (!!!) don't use this API. Messenger Lite does, as do Google Keep and Amazon Chime (!!!). Android doing Android things ¯\_(ツ)_/¯
- daveoc64 4y ago>Telegram, WhatsApp, Signal, Google Messages (!!!) don't use this API. That's a perfectly valid choice. App developers of that size have the resources to make their own camera UI, and produce the experience they want to.
- oblio 4y agoAnd the experience they produce on Android is worse than the iOS one, because Android apps are second-rate mobile citizens.
- daveoc64 4y agoIt's the same on iOS too. Many major apps make their own camera UI, because it allows them to make a bespoke experience that actually feels like something that's part of their own app. There's always the option to use the standard camera app, but that will feel jarring to most people, as it's just not how the most popular social media apps work.
- jve 4y agoWhatsApp is the one that should adopt it.
- oblio 4y agoOn my phone, with about 6 messaging apps, about 40 of them use it. Yes, the vendors are directly to blame, but this stuff should be enforced. The main apps I use, WhatsApp and Telegram, don't use it. So for 95% of my use cases, it doesn't exist :-( Google should crack down more on apps.
- daveoc64 4y ago>Google should crack down more on apps. Crack down on what? You seem to seriously misunderstand the situation. There are two options for an app to take a photo: 1) Using the Camera Intent 2) A custom-designed UI that uses the Camera/Camera2/CameraX APIs There is no one valid option - both are appropriate to use in different cases, and each has upsides and downsides. It's generally going to be the case that both developers and users will see option #2 as the better experience - despite what you might think.
- oblio 4y agoI bought a Samsung smartphone. The smartphone has a bunch of cameras. They can zoom to different levels. They can use AI to do stuff like auto-detect documents and turn on a very smart document scanning mode. Then I open up Telegram or WhatsApp and I'm greeted with a barebones camera app that can't really even zoom. How is that a good user experience?!? In what world?
- rickdeckard 4y ago> How is that a good user experience?!? In what world? In the world of Telegram and WhatsApp, where the own vision and strategy of their camera user experience are valued higher than handing off the task of image-taking to the default camera application. Really, the decision is in the hands of the App developer, the Android platform is offering both paths. The idea is that CameraX combines a bit of both worlds, with vendors like Samsung integrating features there and App-Developers using this toolbox instead of directly calling the API of the camera hardware.