I feel like I'm going insane. On every single model revealed today, there is a differently-colored patch on the right side of the phone, below the power button. What is it? It's not the SIM card slot - that's on the left side. It's not a new TouchID sensor - the website doesn't even mention it at all. And yet it exists in every single render.
iPhone 12 and iPhone 12 Pro
221–230 of 1001 posts
Re: iPhone 12 and iPhone 12 Pro
#222Earlier quoted context omitted.
True. MagSafe is what got me. Apple is genius in how they keep pushing accessories part of the ecosystem.
They must be really confident with their drop protection because I don't know a single person who doesn't have their phone in a case.
Re: iPhone 12 and iPhone 12 Pro
#223The most disappointing aspect to me is that the difference between the Pro and the Pro Max is no longer just the size. I'm quite fond of the size of my 11 Pro and I don't really want to be upsold to the Pro Max if I want the best.
Hasn't it always been the case that the Pro Max has a better camera package?
Re: iPhone 12 and iPhone 12 Pro
#224Earlier quoted context omitted.
True. MagSafe is what got me. Apple is genius in how they keep pushing accessories part of the ecosystem.
They must be really confident with their drop protection because I don't know a single person who doesn't have their phone in a case.
Re: iPhone 12 and iPhone 12 Pro
#225There are two reasons I haven't switched over from Android. I wish Apple would try and fix them: * The lack of a way to move Whatsapp messages between platforms. (They'd just need to allow Whatsapp to use Google Drive for backup on iOS) * The lack of (physical) dual-SIM.
Re: iPhone 12 and iPhone 12 Pro
#226I feel like I'm going insane. On every single model revealed today, there is a differently-colored patch on the right side of the phone, below the power button. What is it? It's not the SIM card slot - that's on the left side. It's not a new TouchID sensor - the website doesn't even mention it at all. And yet it exists in every single render.
Re: iPhone 12 and iPhone 12 Pro
#227Re: iPhone 12 and iPhone 12 Pro
#228The most disappointing aspect to me is that the difference between the Pro and the Pro Max is no longer just the size. I'm quite fond of the size of my 11 Pro and I don't really want to be upsold to the Pro Max if I want the best.
Hasn't it always been the case that the Pro Max has a better camera package?
Re: iPhone 12 and iPhone 12 Pro
#229https://www.apple.com/iphone-12/
https://www.apple.com/iphone-12-pro/
Also: don't miss that there are multiple pages of comments in this thread. You can get to those by clicking More at the bottom of the page—or do it like this:
https://news.ycombinator.com/item?id=24767378&p=2
Re: iPhone 12 and iPhone 12 Pro
#230Earlier quoted context omitted.
When your business model revolves around marketing and aesthetics, you need to put the extra effort. You can tell Apple's target demographic isn't enterprise markets at every turn.
One could argue that a company like Stripe's target demographic is _precisely_ the enterprise markets; yet, their product pages are slick af! Smooth scrolling, animations and all that jazz. Because they're made up of folks who love JavaScript (and animations, of course) Apple's marketing team is similar. They're probably a bunch of people who _love_ making videos; probably studied film or art or spent a ton of time o…
Where Stripe absolutely nailed it is the infrastructure around it. Their SDK documentation and continous improvements still outpace Braintree.
For instance, Stripe has custom elements that you can use to interact seamlessly with their SDK, with little setup needed[0]
I could not find a similiar integration from Braintree.
Compartively, I find their informational SDK page a bit more polished than Braintree, respectively, though I realize some of this is personal style and taste, Stripe has clear pathways for me to find the information I want right on the side bar and referenced throughout the landing page for the client SDK[1] where as Braintree[2] is more narrowly focused, which with payments, may mean I miss a better set of features I should be aware of.
Reducing frictions and painpoints is what they won with, in the end. It was easy to setup and maintain. How many 3rd party services have both of those things that handle something as complex as payments? I can't even get AWS integrations with their own SDKs working together without some effort
[0] https://stripe.com/payments/elements
[1] https://stripe.com/docs/stripe-js
[2] https://developers.braintreepayments.com/start/hello-client/...