Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It seems like we’re not getting the full story. Assuming there was an API that delivered this data to the app, did the cost for using this go up and make it difficult/impossible for the app developer to make anything at their current rate? We’re shipping companies concerned about privacy issues with this data being stored on a third party server (if that’s how it works)?
I’m willing to bet you’re probably correct on the API cost. Whenever functionality like this “breaks,” it’s usually because the other party has increased the price of accessing the data. Deliveries could scrape fedex.com for the data as a workaround, and FedEx could then block them. (Maybe this was already happening.)
 
  • Like
Reactions: Kierkegaarden
You act as if this is up to the developers in the first place. Customers caused the pricing race to the bottom when the app store came out. Assuming a 30% profit margin (considered razor thin in almost every other industry), and a year over year increase in costs of 10%... According those projections, let's say the $4.99 piece of software actually costs $3.49 to run for that first year. With the estimated cost increase, that would cost $57.65 for 10 years. With that 30% profit margin you'd have to charge closer to $81.99 up front.

And bug fixes and updates are inevitable. APIs change, even if you're just relying on the APIs for the OS. Hardware changes... Security flaws are found in the programming language, or the underlying operating system...

You don't understand the reality of development, or the economy of the app store.
I do understand it. When you have every high school kid in the world wondering if they can make the next Flappy Bird you will have some competition. That's fine.

A feature isn't an app. Businesses need to do a cost analysis. That's on the developer to do. If they can't survive on $3.49 then maybe they shouldn't make the app.

No developer should think they can survive on a single app. That's not reasonable.
 
I don't discount that the subscription model has merit, I only point out that the merit is for the developer not the customer. There is value in high entry costs as it keeps fly-by-night ideas from cluttering the app store and keeps those not interested in running a business out. Software shouldn't be released in beta form. It's not up to customers to build software - that's on the developer. The risk should be on the developer. We don't see the same risk in software that we see with other businesses. A baker might lose their house because their idea didn't end up turning a profit, but developers just wash their hands and try a new app.

The benefit to a one-time payment is that the developer needs to come up with another product. They can't make their business a calculator app, or an app that tracks packages already being tracked. Those are the sort of apps we see with subscriptions - low innovation AND low risk.

Instead, we see subscriptions that transfer risk to customers. That's not acceptable. If it's not a viable product release it free or find a way to turn it into one. Deliveries should have been a feature of Delicious Library, not its own app.

The only reason current software has more ongoing costs than previously is because current software is tied to a software as a service model. It's not intrinsic to the app itself. But the truth is, that most developers don't use subscriptions. That's what happened here. Heck, most don't use IAP either. We see it mostly with mobile apps because the cost of entry into these markets is so low. It's easy for a developer to come up with a feature and market it as an app. And since they don't have any other ideas, or interest in performing market research to find out how much their product is actually worth they just tack a subscription onto it. Honestly, they don't even care if it generates a lot of revenue, because they play the long game. Enough people over time will try the app and that will generate money - even if they don't provide any updates or add any features.
Interesting thoughts — I will add that the App Store created the low barrier for large scale mobile software distribution, and that is good for developers. Good and bad for consumers — good for the wide variety and lower price of software — bad in the low barrier for entry that has produced poor software and issues such as what you describe.

I suppose another issue is control of the data — anytime an app uses third party data and tries to monetize this, they are beholden to the third party and it’s only a matter of time before that third party will want a larger piece of the action.
 
Did you read all 7 pages or just part of one post? The very first thing I said was that they needed to charge more. The issue isn't should they get paid. It never was.

It's not the responsibility of the customer to figure out the cost to make the product. That falls on the developer. Figure out how much the product can make, including projected costs, and then determine if you can build it for less.

Most apps will fail. Correct that, should fail. This app was a feature, not a product. It should have failed years ago because it never matured into a full-featured solution. And that's the issue with software. It can sit on the shelf for years and the developer still makes the same profit when someone buys it. It's not like the developer's 70% degrades with time, in fact, they get more money because after a year they get 85% instead of the 70%. Payment is stacked to encourage subscription payments.

Presumably you didn't read all my post where I discussed up front payment models.

In addition how would you feel if you paid $49.99 for this app only to have it break after one year?

How's your model work out then?
 
Good god.

Everyone hating on $5 subscriptions while they use $1000 iPhones.

It just cracks me the heck up.

Same, I personally hate subscription apps but $5 for a year, not a month for an app that provides me with so much convenience is worth that tiny price. Seriously, it's $50 a decade, not exactly expensive compared to a lot of other apps that charge more than $5 monthly.
 
As in pay once, use forever at no extra cost.
Cool, so not a free ride since there was an up-front cost.

Regardless, I’m glad a dev who shoehorned subscriptions into their previously useful app is now stuck with a nonfunctional one. It’s a good start, time for more sub-happy devs to go under
 
  • Like
Reactions: Ash Pole
Cool, so not a free ride since there was an up-front cost.

Regardless, I’m glad a dev who shoehorned subscriptions into their previously useful app is now stuck with a nonfunctional one. It’s a good start, time for more sub-happy devs to go under
You're happy a Developer is habit g problems leading to a loss of functionality?

Wow... Sounds quite callous.
 
You're happy a Developer is habit g problems leading to a loss of functionality?

Wow... Sounds quite callous.
I do a bad job at work? I lose my job. I decide to just stop supporting a file or macro I created? Guess what, I lose my job.

People don’t get a free pass just because they decided to sit on their computer longer than the average person while not being salaried. That just makes them either a bad negotiator or a gambling addict thinking they’ll come up with the next million dollar app
 
I would advise that Mike Piontek put an alert into the next version of his app showing where users have to call to complain. If enough of us do that, maybe FedEx can be moved to even provide an API.

After all, we are the customers of these package carriers.
 
  • Like
Reactions: suns93
I do a bad job at work? I lose my job. I decide to just stop supporting a file or macro I created? Guess what, I lose my job.

People don’t get a free pass just because they decided to sit on their computer longer than the average person while not being salaried. That just makes them either a bad negotiator or a gambling addict thinking they’ll come up with the next million dollar app
Your loss of job affects you.

A Developer losing their livelihood not only affects them, but people who paid for and use the app.
 
Darn, this was a great app. Having to go through all the other apps to track stuff sucks.
 
Your loss of job affects you.

A Developer losing their livelihood not only affects them, but people who paid for and use the app.
I’ll remember this next time I make an app that is basically a reskinned google query with notification capabilities

Ooh, and charge $ for it, and a few years later change to a subscription based model
 
Sounds similar to what developers will start saying once they get their own payment method, still have to pay apple, and the nightmare of running it all without a great backend system like Apple already has.
Developers aren't asking to get (just) their own payment method.

Give us the ability to distribute apps with no involvement from Apple.

Apple wants to withhold Xcode from us? That's fine, I'll use an IDE from JetBrains or something open source. The App Store? I'll use Epic's or Valve's or Amazon's store or roll my own.

Apple provides extraordinarily little of value to developers. The primary thing that Apple does is engineer barriers to maintain their position as a pointless person in the middle that everyone has to pay. Apple's behavior is generally known as Rent Seeking.
 
Apple provides extraordinarily little of value to developers.
Aside from an entire library of API calls, documentation, and tools.

Yup, nothing at all.

Apple wants to withhold Xcode from us? That's fine, I'll use an IDE from JetBrains or something open source.
Still need xCode. How else you going to interface with iOS?
 
I do a bad job at work? I lose my job. I decide to just stop supporting a file or macro I created? Guess what, I lose my job.

People don’t get a free pass just because they decided to sit on their computer longer than the average person while not being salaried. That just makes them either a bad negotiator or a gambling addict thinking they’ll come up with the next million dollar app

BTW what if your CEO does a bad job? Then how about you all lose your jobs.

That sit well with you?
 
If I knew where to send the email I’d be happy to tell FedEx I’m picking other carriers for inbound shipping when I order stuff, if they want to be uncooperative with the Deliveries app. The additional motvation is that they have been a total FU mess lately, with delayed and lost packages.
 
Wow. Deliveries has been on my Home Screen & dock for many - many years. I don’t know. 7 years? Anyway, what a total bummer. No fault of theirs but I feel so bad for the team behind these great applications.
 
  • Like
Reactions: suns93
Aren’t they just scraping data from the delivery agents’ website? So it’s the delivery company paying for server costs, with the Deliveries app piggy backing off them.

Chances are they use their own infrastructure to batch up API calls to be most efficient.

Just to be clear: I used to use Deliveries until they went subscription. I decided that for me the app wasn’t worth the subscription.
 
  • Like
Reactions: suns93
Aren’t they just scraping data from the delivery agents’ website? So it’s the delivery company paying for server costs, with the Deliveries app piggy backing off them.
They run servers to allow syncing data between devices without iCloud. Push notifications also require the developer to run a dedicated server, though I’m not sure if that’s the case here.
 
Deliveries *wipes the floor* with Parcel in terms of design though. It’s not even close. Ugh. I’m still rooting for JuneCloud and Deliveries. Hope they can fix FedEx.
 
Always a risk when something you do depends on building off the infrastructure of someone else
Same thing can be said with Apple's own services. Apple Music, AppStore for various Apple devices, Arcade. Nothing is certain when you involve 3rd party into the equation.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.