|
| ▲ | cschep a day ago | parent | next [-] |
| I would get a little bit of joy if a duo user noticed the effort I put into making my app work well on their device. Why put effort into anything? Your take is bordering dangerously on cynicism. :) |
| |
| ▲ | matsemann 21 hours ago | parent [-] | | No, it's based on pragmatism. Every feature is a cost/benefit tradeoff. You didn't answer the question: would it be worth it? |
|
|
| ▲ | matwood 21 hours ago | parent | prev | next [-] |
| > But will you gain anything by building for it? We're not talking about 0/1 here. There's making sure the app works and looks ok on the Duo and then there's building out Duo specific features. The works/looks ok is generally pretty easy with new devices. Just build with the new SDK and fix places where the app wasn't doing something likely already suggested by Apple. A big one will be safe areas which people often ignored except on the top and bottom. |
|
| ▲ | wat10000 a day ago | parent | prev | next [-] |
| As a user, this attitude makes me sad. As a professional programmer, it at least gratifies me to know this is the attitude I'm competing against. |
| |
| ▲ | matsemann 21 hours ago | parent [-] | | Thanks for the backhanded compliment, very mature.. I'm not an iOS developer, never made an app at all, I asked because I'm curious. What is it really to gain? | | |
| ▲ | wat10000 13 hours ago | parent [-] | | I just happened across this video with Apple’s new CEO and how Apple does things: https://youtu.be/4pqF5KMHOr8 He talks about a Steve Jobs story where he moved a piece of furniture and notes that the back, which would be against the wall, was still finished as nicely as the front, even though you’d never see it day to day. He compares this to Apple products being beautiful on the inside as well as the outside. Even the cheapest products are like this. There’s another story going around about the new guy, from his early days working on an Apple display. He was inspecting a supplier and discovered that the screws in the back had 35 grooves on the head versus the 25 specified. He ended up arguing with the supplier and making them fix it. Not because the grooves were core to the product, but because it’s important to get things right. In short, craftsmanship. Build things well. Take care of the details. Make your stuff beautiful even if only a few people will ever see it. Even if nobody will ever see it. Sure, an app maker could say, the Duo will be a small percentage of our user base, who cares if our app looks like shit to them. And quite a few of them will, I’m sure. And people will notice that these apps look and work like garbage on some of their friends’ and families’ phones. And this attitude will not confine itself to this one thing. These same app makers will say, who cares if this button is a little clipped. Who cares if the screen flashes during launch. Who cares if it takes five seconds to launch. Will we lose a noticeable number of users? And that’s how we end up with legions of apps that are hot trash. Many of them will do fine despite that. My health insurance’s app is hot trash and they’re not losing me as a customer. But the company that makes the hardware and software their app runs on is way more successful than they are. Obviously a big part of that is down to what industry they’re in. But some of it is because Apple finishes the back of their furniture. | | |
| ▲ | matsemann 8 hours ago | parent [-] | | But you're kinda proving my point. I don't disagree with having pride in your work and obsessing over details, but as you say, it won't matter in the end. And so, many will probably find themselves disappointed with the Duo, as there is little reason for developers to care. And then many won't. | | |
| ▲ | wat10000 6 hours ago | parent [-] | | I’m saying it does matter in the end. Partly because small numbers still count, partly because the “who cares” attitude gets infectious and impacts everything. App makers aren’t just going to ignore the Duo while making everything else perfect. They’re going to ignore the Duo and ignore graphical glitches and have terrible launch time and terrible accessibility and on and on. At the end of the day, they may have enough of a captive audience that they still make good money, but that’s not the same as it not mattering at all. A good app is a competitive advantage, even if the effect is just in the margins. And my point is more about us as individuals. As a user I want better apps. As a developer I care about doing things well, which translates directly into career success. |
|
|
|
|
|
| ▲ | echoangle a day ago | parent | prev | next [-] |
| You could say this about every QoL feature though. That’s not a reason to not do it though, it adds up and at some point other apps that do bother to make their apps as good as possible will become more popular than yours. |
|
| ▲ | fragmede a day ago | parent | prev | next [-] |
| Can two people use opposite sides while in tent mode? Because that makes for some fun in-person games. |
| |
|
| ▲ | busymom0 a day ago | parent | prev | next [-] |
| Duo users also likely have disposable income to spend on in app purchases, maybe click on ads to purchase things, and other monetization. So I do think it's worth building for it. |
|
| ▲ | reaperducer a day ago | parent | prev [-] |
| But will you gain anything by building for it? Nothing ventured, nothing gained. Will you see noticeably more users or people choosing another alternative because you didn't specifically building the app for Duo? I haven't done iOS development in a long time, but my understanding is that if your iPhone app is designed well and uses all of Apple's recommended methods, adjusting for different screen sizes and orientations is fairly easy. If you decided to go cheap/easy/dumb from the outset, then you made your bed, and now you get to lie in it. |
