3 ms·
I’m not angry so much as just annoyed with the glibness of “well you can just do this if you ignore the actual use as a product” Like, sure you can do any numb
by dagmx 3y ago
I’m not angry so much as just annoyed with the glibness of “well you can just do this if you ignore the actual use as a product”
Like, sure you can do any number of things if you don’t consider how it’s used at all or what the user experience is.
- tsunamifury 3y agoWorked for 10 years on hardware/software integration design with Apple and Google. I am not ignoring the actual use case, I think you just aren't exactly able to conceptualize how the application of how this works. You use the camera normally, the software does all the crop/rotation/overlapping augmentation -- just like the smooth zoom between cameras already does. User knows nothing. Only issue would be if crop overlaps lens positions can't be normalized. But we already did that with smooth zoom.
- dagmx 3y agoEven if we throw out all the technical considerations, you’d still be asking the user to hold the phone diagonally to get the stereo alignment. If instead, you said “hold it normally and we crop/rotate for you” , you would now have two point of views at different heights, you’d have very uncomfortable depth perception. There’s not a solution here that would work with the 14 Pro camera layout unless you used the telephoto and then cropped the wide angle to match. In which case you now have the issue that your users are stuck in effectively a 70mm fov which isn’t very useful for most use. Again, I think you’re ignoring many aspects of the product design to try and say it’s possible.