News for hackers. Stuff that matters.
Re:Reverse-engineering the Starbucks ordering API by rconti on Wednesday July 12, 2017 @11:13PM (#14758461)
Excellent writeup.

I have to take issue with the "Starbucks app is great" line, though. I think I've had more problems with it (on iOS) than any other app. It's the only app that (for a period of many months if not a year) was regularly unable to find my location. Even if I opened up Maps or some other location enabled app and found my location before launching Starbucks, it would just bomb out.

Overall the app seems to have tons of 'issues'. It's been better the past few months though. And it beats the hell out of standing in a 10 minute line. I honestly wouldn't stop at Starbucks anymore if it wasn't for the app.

Re:Reverse-engineering the Starbucks ordering API by vinhboy on Thursday July 13, 2017 @12:26AM (#14758698)
Agreed. I'd also add that the UI for the app needs work. Ordering coffee for a group of people becomes a huge hassle on my phone because their search is not precise, and customizing drinks is a bit cumbersome.

I spent like 20 minutes trying to order 5 drinks the other day. It was also annoying because when I left the app, all my selected items disappeared.

Re:Reverse-engineering the Starbucks ordering API by CodeWriter23 on Thursday July 13, 2017 @03:07AM (#14759318)
I'd call that an app fail, taking more time to use the app than writing a list then walking there and back with your complete order.
Re:Reverse-engineering the Starbucks ordering API by sluggg on Thursday July 13, 2017 @12:43PM (#14762798)
I would not. Ordering a large group of people drinks from Starbucks is not in any way the primary use case for the application. For it's primary use cases (paying at the store, rewards redemption/collection, ordering yourself drinks ahead) it works perfectly.

Additionally, if you think about the feature set that would be required to facilitate bulk orders then you will quickly find that it would be quite large feature set and require it's own flow. The app does has new-ish features that allow you to re-order prior orders and save drinks, which would help for these bulk orders, so they are making progress. If you are consistently ordering drinks for a large group of your co-workers then you can save their drink preferences and boom.

Re:Reverse-engineering the Starbucks ordering API by CodeWriter23 on Thursday July 13, 2017 @07:46PM (#14766277)
Of course it's not the primary use case and the app guarantees it never will be. I can say from my experience that sending a gopher to get everyone coffee was a twice daily occurrence at our family business in NYC. Shave 5 minutes off that time and we would go to Starbucks instead of the deli.
Re:Reverse-engineering the Starbucks ordering API by veritas3241 on Wednesday July 12, 2017 @11:30PM (#14758513)
I just wish I could customize the requests on breakfast items. I want no cheese on my sandwich. I can request it in person. Can't on the app.
Re:Reverse-engineering the Starbucks ordering API by djrogers on Thursday July 13, 2017 @12:25AM (#14758693)
Select the sandwich, tap on Sandwich Options, tap the google for No Cheese. You've been able to customize orders for as long as I've been using it to order stuff.
Re:Reverse-engineering the Starbucks ordering API by novia on Thursday July 13, 2017 @08:46AM (#14760782)
I have also had issues, except on Android. Admittedly, I am using a rather old smartphone now, a Note II, which my carrier has only allowed to update to Android 4.4.2.

Whenever I try to order something through the starbucks app, I have to try multiple times because at some point in the ordering process the message, "unfortunately starbucks has stopped," or something like that will pop up and the app will close. Usually no progress is saved. Often it will crash right as it is processing the payment, and when I open it back up I have to go to the order history to check to see if it went through. Usually if I make it that far before it crashes then my order will have been submitted successfully.

I would love to be able to skip the UI and just submit my order an alternate way, but maybe the answer is to just stop being so cheap and to get a new phone.

Re:Reverse-engineering the Starbucks ordering API by gmemstr on Thursday July 13, 2017 @01:07PM (#14763014)
Here's a little story about how my gold card was disabled;

I was ordering coffee and my balance wasn't quite sufficient. I reloaded it via PayPal, but the balance didn't update so I tried again (it did error out). The app crashed, I reopened it and found it had added both transactions to my account. Open dispute on PayPal for just one of the transactions, got a refund but my card was completely locked out - $0 balance, couldn't reload it (the dispute was after I tried contacting support). So now I don't go to Starbucks.

Re:Reverse-engineering the Starbucks ordering API by torstenvl on Thursday July 13, 2017 @12:56AM (#14758832)
Agreed. The app has definitely sent a different order than was on screen before; until recently it refused to work with Apple Pay unless your Apple Pay address matched character-for-character what your bank had on file (if one used # and one used APT, or one used VA and one used Virginia, it would fail), and we've lost the ability to customize orders as much as we used to (e.g. you can no longer order a flat white with chai unless it's saved as a previous order).
Re:Reverse-engineering the Starbucks ordering API by jsjohnst on Sunday July 16, 2017 @04:35PM (#14784000)
Was the card an Amex by chance? Visa and MC only use the numerical digits in address and the zip code for AVS checks.
Re:Reverse-engineering the Starbucks ordering API by nickplee on Wednesday July 12, 2017 @11:25PM (#14758489)
Strange. I've never had a problem with it.

And yes, it makes the coffee taste better.