qzervaas

This is not true. Many app developers use the affiliate program from their app's web site to claw back some of the 30% commission.

Minimise the house take, so to speak.

That's all well and good - and many people realise and accept this - but the degree to which you're the product can clearly vary wildly. That's the real issue.

But the rebooked seat doesn't displace somebody on the next flight, so what's the actual cost?

Because he can?

I'm not sure what the OP had to learn exactly in doing this, or whether he knew it all already, but it's far easier to learn stuff when you have a practical application to apply what you're learning to.

This is such an example, and other people could learn a thing by the approach.

(Although personally I agree, automating is often premature optimisation)

Inexcusable may be strong - but I wish I could find the thread I was referring to.

Perhaps they were working on it for a long time, but they were actively defending their stance for years after many people were requesting this, and after many incidents of Play Store apps intentionally doing more than expected (uploading contact lists, tracking location, etc...).

As someone who has developed and published Android apps, it was super frustrating to spend half your app description justifying each and every permission used, and still getting negative reviews simply because you had to request some scary looking permission for the most mundane feature addition.

Wait a minute - users were requesting for years that Google change the permissions model of the Play Store from upfront to runtime permissions (like iOS does).

Google constantly shot that down and said how it works (agree to everything before downloading) was intentional and expected behaviour. They have finally changed that model now, but in my opinion this was pretty inexcusable and reckless.

I was unable to find the issue in the Android bug tracker now, but it's a pretty long thread.

This theory is pretty easily debunked when you consider the primary goal of bitcode is to strip assets from apps that aren't relevant to a user's device, hence taking up less space.

(For example, removing @2x images for a plus device that uses @3x images, or vice-versa).

Completely agree. At the same time though even if it's a 5% rate of feedback, that's still valuable, I just wish it was higher.

(Hence my defense of Planet having TOS requiring feedback for their beta).

How dare they!

Seriously though, I'm an indie iOS developer with a semi-popular app. I have hundreds of TestFlight users, but I only get feedback on betas from a handful.

This can be frustrating, considering the whole point is to get things right for many edge cases before it leaves beta.

Did they ever have good support?

One of their key selling points to me over Fitbit is that they support HealthKit on iOS.

However, there was a critical bug that prevented the HK integration from working properly.

As someone who knows HealthKit pretty well, I went in circles for weeks trying to get them to fix it - every response would reset the thread back to the agent walking me through basic steps, no hint of reading the ticket history.

Super frustrating, so I just stopped using it at that point.

I don't mind the lack of MagSafe connector on the new MBP. What I do miss however is the green/orange light to know when it's fully charged.

That's something they could have kept (somehow) in the shipped USB-C charging cable.

At least NZ has fibre. Unlike the western island (Australia, aka the mainland ;) ) which has an absolute shitshow for Internet connectivity.

There are likely no significant financial gains to be made outsourcing to Australia. It is super expensive here for everything.

Not an even comparison.

Any explanation for the downvotes?

One thing that the US-based HN crowd do well is mobilise in order to contact their local politicians. Australians aren't so inclined generally.

In case you are though, you can contact Prime Minister Turnbull through this form:

https://www.pm.gov.au/contact-your-pm

This thing is supposed to last more than 3 years into the future.

For those who are unaware, NBN stands for National Broadband Network, the Government-funded project to bring "high speed" Internet to all of Australia, both urban and rural.

This article is about comments the CEO of the NBN company made yesterday.

Does anybody know the process for these companies being involved? Did somebody ring around and organise this, or does word just get around and companies request involvement, or something else?

No Yahoo either.

He says a lot of words. Many are false, some are true.

I don't understand how everybody (well, many people at least) ignore the obvious pathological lying and conclude he's doing what he said he would.

Who are you going to report the anomaly to when you flip a coin 10 heads in a row, and what is a satisfactory resolution?

No, it'll still be self-selecting:

Good developers who actively respond to reviews will improve their apps. Somebody who left a low review due to a misunderstanding now has a chance to increase their review because of a diligent developer.

A developer who doesn't care and/or doesn't monitor their reviews will not turn that user around.

My biggest issue with the cost breakdown is the omission of:

"Cost of redeveloping entire app natively when a cross-platform framework limitation is hit."

This is common for non-native development.

Facebook's apps are the not the first place I would look for model example of "how things should be done" in (native) apps.

It feels like the UI is changed quite frequently, which when you combine with the bugs and various anti-patterns (out of order content, making basically any activity appear in the "globe" notification, messenger opening another app, unable to find old posts, etc, etc..), it's a super-irritating experience at all times.

Not a fair comparison. Those updates can happen in the background (when in another app, when you're asleep, etc.), and most apps will continue to operate without being updated.

Nothing more irritating then being forced to update / download content when you need to go and quickly do something in an app.

It's quite easy to customise. A lot of people's complaints are along the lines of "no bookmarks manager", but while not UI-friendly, ~/.ssh/config is as powerful as it gets.

Can you elaborate on the unusability of Terminal.app?

It's one of my most used apps and I have no issue with it.

Also, I didn't know many of these until recently:

http://mjtsai.com/blog/2016/09/26/mac-terminal-tips/

For those who have just updated to macOS Sierra, the default SSH client configuration is to not allow ssh-dss keys any longer.

Follow these instructions to update your keys.

Exactly - I just meant not the default popup as soon as you launch without any explanation or justification.

This is what developers would do in the past with location access also, but as privacy awareness takes hold people are far more likely just to deny these permissions.

In iOS it's a pain for a user to actually reenable the setting after the fact.

> should have been done at launch

Generally speaking, this is the worst way to do it, as the app hasn't made a case for why it needs to send notifications.

It should do it in a contextual way so the user understands that notifications will enhance their experience of the app.