471–480 of 512 posts
They killed the SE! Now we're stuck with screens too big to use with one hand. I really really dislike this.
SE is awesome for travel where you want the phone to fill certain critical needs then stop distracting you. There will be a thriving SE market on eBay.
They presented the dynamic depth control with the words: "No other smartphone right now can do that". Lie. I'm writing this comment on a Vivo Nex and I have been using this for months.
No, the Vivo Nex cannot adjust depth of field in post-processing. It can adjust depth of field (via aperture) before capture.
Earlier quoted context omitted.
Not disagreeing with you, but as a developer, I'm happy that we can now do UX design for 4.7-inch phones, and prevent installation of our app on smaller phones. You do that in an indirect manner, by requiring NFC, thus eliminating 4-inch phones, which don't have NFC: https://developer.apple.com/library/archive/documentation/De... (Cmd-F nfc). If Apple had updated the iPhone SE with NFC, this trick wouldn't work any m…
Just curious, since I'm not a mobile developer, is most app design done with pixel perfect layouts now? I vaguely remember watching a YouTube tutorial years and years ago (iPhone 4 I think) about making apps and many of the interface elements would expand/contract to the devices screen. Not bashing on your decision, just generally curious. If so, that sounds like a lot of work to make custom interface layouts for a h…
Taking your example of expand/collapse, when you implement it, it's more complex than it appears when watching a Youtube video: you now have to handle three states: a collapsed state on small screens, an expanded state on small screens, and big screens, which don't have expand/collapse. This imposes more work on the designer to design for these states and make sure they're all usable and look good, perhaps with animated transitions between them. On the engineers, who have to deal with multiple code paths and edge cases. On QA, to spend more time trying to test more scenarios on different devices. Everything sounds simple till you code it up :)
Now, if you could eliminate this complexity by not having to collapse the control in the first place, that would be simpler. Maybe there's enough space on the 4.7-inch screen for that.
UIs scale up better than down. I prefer to do UI design for the smallest supported screen size. If we choose to support 4-inch screens, we may have to choose a UI design that's not optimal for 4.7-inch and bigger screens, which the majority of our users actually use. Whereas if 4.7 was the baseline, we may be able to come up with a better design for most of our users.
All these problems are, of course, solvable, but if they take X amount of time to solve, is there something more beneficial you can do in that time?
They killed the SE! Now we're stuck with screens too big to use with one hand. I really really dislike this.
2 years ago got a 7 over a 7+ for single handed use felt the SE was too small. Now, I'm just so at ease on the rare occasion that I get to use it. Said owner doesn't like it claiming its 'slow'. I on the other hand just may switch over to a refurb SE.
They killed the SE! Now we're stuck with screens too big to use with one hand. I really really dislike this.
As an SE user, me too. I wished they would have done a refresh for the SE.
Perhaps its a software and bloat issue, but the only noticeable thing improvements have been better pictures and I can read more on a single page-view, but everything else seems exactly the same.
It was interesting to hear apple state that one of their goals for building products was to make them last longer in order to minimize waste. People often accuse hardware manufacturers, including apple, of intentional obsolescence. I am interested to see if they actually change anything about their process, software and hardware, to put any weight behind this claim, or if it is just marketing doublespeak.
Here's one example, Apple will still repair the iPhone 4 which started selling in 2010 and was discontinued in 2013. https://support.apple.com/iphone/repair/service
Earlier quoted context omitted.
Not disagreeing with you, but as a developer, I'm happy that we can now do UX design for 4.7-inch phones, and prevent installation of our app on smaller phones. You do that in an indirect manner, by requiring NFC, thus eliminating 4-inch phones, which don't have NFC: https://developer.apple.com/library/archive/documentation/De... (Cmd-F nfc). If Apple had updated the iPhone SE with NFC, this trick wouldn't work any m…
That sounds directly user-hostile. Imagine if HN's web server served 401s to everyone with a Mozilla user agent.
Guess what's worse than an app that doesn't support your particular model of iPhone? An app that supports all possible devices and configurations, but that doesn't solve a problem users care about. Then all the time and resources that went into it go down the drain.