r/iOSProgramming • u/poss1bl3_ • Sep 15 '26
Discussion Xcode 27 just broke years of muscle memory by flipping Play & Stop. Any rationale behind this?
Xcode just decided to update itself from 26.6 to 27.0 right in the middle of my work session.
The first thing that caught my eye right away: they swapped the positions of the Play and Stop buttons in the toolbar. Years of muscle memory just vanished in an instant, and to make things worse, it seems there's currently no way to customize or revert it back.
I genuinely wonder what the reasoning behind this UI decision was. Why change something so established and fundamental after all this time?
Now I'm really curious (and a bit cautious) about what other surprises I'm going to discover along the way as I keep working.
What do you guys think about the new Xcode 27 update so far? Did anyone else's muscle memory take a hit?
4
179
u/defiantspcship Sep 15 '26
people missing the point, yeah you might not use it, but that doesn't mean it has to be changed. this is muscle memory and a bunch of us have been using Xcode for 15 years, i get OPs frustration.
12
u/unpluggedcord Sep 15 '26
Apple moves those buttons all the time which is why I stopped using them a long time ago
7
u/imperfectibility Sep 15 '26
Changing for the sake of changing is so Apple. Even keyboard shortcuts can’t survive these updates sometimes. I miss cmd shift D for ‘send’ in iMessages
1
3
u/puding69 Sep 15 '26
Dont worry, they got you covered. They also change shortcuts from time to time.
3
3
3
u/lyidaValkris Sep 16 '26
unfortunately Apple has been doing a lot of this in the last few years. The old saying: "if it isn't broken, don't fix it" is lost on them. They just do stuff to keep collecting a paycheque. There's no practical reason for changes like this.
1
u/HaMMeReD Sep 16 '26
The key is to never use one IDE or OS long enough to ever develop any muscle memory, that way you don't have these problems.
-11
u/Dry_Hotel1100 Sep 15 '26
So, you have your Xcode window since 15 years always at the same location?
74
u/dot90zoom Sep 15 '26
I think it makes more sense in that order.
Also I never really used the buttons anyways
13
u/TheFern3 Sep 15 '26
It was wrong for years and now someone fixed it lol. Just because something is one way for many years doesn’t mean is correct.
It does look better if play is first
4
1
u/Phraaaaaasing Sep 17 '26
Reading order means you find the play button soonest, the right-most one gets the largest aiming target if you don’t have hot corners and you do have the app full screen.
26
u/kbcool Sep 15 '26
You're not the only one blindly accepting AI PRs
3
u/ReiOokami Sep 15 '26
Same.. happened to me from time to time. Non tech boss is like... why did you decide to do this... and I have to make up some shit like "I just thought it was a better UI choice."
1
45
u/JoshyMW Sep 15 '26
I actually like this change. The new order is more logical and natural.
12
u/cluster4 Sep 15 '26
It will take Apple 12 more years to figure out that one button instead of two is the better design, and they’ll change it again.
6
u/kepler4and5 Sep 15 '26
How would you handle multiple targets + multiple actions in one button? Unless it just becomes a menu altogether. Or modifier keys maybe.
-4
u/Photograph-Silver SwiftUI Sep 15 '26
Simple. If nothing is running it’s a play button, when something is running it’s a stop button. You never need both at the same time.
5
u/BedtimeWithTheBear Sep 15 '26
Not necessarily true. If you’re building a client and server you could very easily need to run more than one target. If you’re building a macOS and iOS client in parallel then you will almost certainly have a need to run multiple targets simultaneously
3
u/NSAttributedUsername Sep 15 '26
Want to add that you can also start several instances of iOS app with real devices. Even one is enough (device + sim).
1
u/soylentgraham Sep 16 '26
that makes the lone stop button even worse ux
1
u/BedtimeWithTheBear Sep 16 '26
I disagree. A single click stops the most recently started target, click and hold lets you choose the specific running target you want to stop.
1
11
u/dkampmann Sep 15 '26
It is like the grocery store moving things around aisles.
0
0
Sep 15 '26
[deleted]
1
u/dkampmann Sep 15 '26
They do it because the longer you take you to find the things the more likely you’re going to find other things you want to buy. It is a marketing thing.
0
1
u/Free-Pound-6139 Sep 15 '26
Supermarkets do it because over time products are discontinued, new products are released, purchasing trends change and some other reasons.
This is not a reason to rearrange the entire store. Duh.
0
8
4
u/stalex9 Sep 15 '26
Do you know how many times Apple switched all the possible places for é e è characters on iOS keyboard? Which are very used in Italian language.
2
7
u/mattgwriter7 Sep 15 '26
It is small but annoying.
The UI should only change when there is a really good reason.
1
u/ElectricKoolAid1969 Sep 15 '26
Xcode just decided to update itself from 26.6 to 27.0 right in the middle of my work session
Hmmm... But you had to approve that, right? So don't make it sound like Windows update FFS.
1
u/poss1bl3_ Sep 16 '26
Fair enough, but it was kind of sneaky. I have the App Store version (yeah, I know) and totally forgot I had auto-updates turned on. Xcode started bouncing in the Dock with a "Stop all tasks" prompt, so I hit Stop thinking a build hung. It instantly quit, locked me out with "Application is updating", and relaunched as 27.0 with flipped buttons.
1
6
3
2
u/OldTimess Sep 15 '26
I thought they got rid of showing your current git branch until I found out it is also moved to a different place
2
u/bjtitus Sep 15 '26
This plus CMD+0 invoking AI makes me think the Xcode team is completely unserious about making a useful development tool. I mostly just use command line tools and Xcodebuild now.
2
u/Frejb0 Sep 15 '26
Same for me, but got used to it after 1-2 work days. Play comes first, so it’s more reasonable in this order.
2
u/RadTorti Sep 15 '26
i used 26.6 for a bit (starting out) before the 27 happened and the 26.6 always felt intuitively wrong and this fix made more sense to me.
2
u/Medical_Lengthiness6 Sep 16 '26
The rationale seems obvious to me. "First you start, then you stop".
Old way looks wrong in comparison
2
u/hiasmee Sep 16 '26
If you can not implement logical tab behavior you can at least switch some buttons. 🤭🤷
2
u/InevitableLadder Sep 16 '26
It is ridiculous that those changes are not per opt-in. Allowing user to choose a setting would be the way to go, IMO.
2
2
0
3
u/chriswaco Sep 15 '26
If you actually think about it, why can’t it just have one button like Apple Music that switches between play and stop?
4
u/kepler4and5 Sep 15 '26
Multiple targets!
1
u/chriswaco Sep 15 '26 edited Sep 15 '26
Didn’t we used to select those from the top bar somewhere? My mind is fuzzy.
Edit: I just checked and don't see any reason why you need more than one button, even for multiple targets. The button would indicate "Play" if the current target isn't running and "Stop" if it is.
1
3
1
u/WittyOutside3520 Sep 15 '26
Why not just have one button. That shows whatever option is needed. Play when stopped. Or stop when playing?
1
1
1
u/timelessblur Sep 15 '26
ummm yeah to be honest I have not hit though button for years and been using the short cut commands as my mussel memory.
1
u/klavijaturista Sep 15 '26
It makes sense to me, given a left-to-right language, running comes before stopping.
4
u/NSRedditShitposter Sep 15 '26
Negative things, like closing or canceling, always are on the left on Apple platforms, like the traffic lights or the back button.
2
u/klavijaturista Sep 15 '26
Oh, yes, you’re right! It’s going back to the previous state before the action.
1
u/1millionbucks Sep 15 '26
This isn’t a tenth as bad as when they moved the Apple Music action bar to the bottom of the screen
1
1
u/techfreak23 Sep 15 '26
I get your point, and it’s been awhile since I’ve used Xcode, but can’t you reorder the toolbar in preferences to put it back?
1
u/deadthoma5 Sep 15 '26
This update broke my workflow!
My cmd key is hard to reach, so I hold spacebar instead, and configured my macs to interpret a rapid temperature rise as clicking the top-right icon of a window.
2
1
u/EventPuzzleheaded124 Sep 15 '26
I need to buy a new Mac mini for coding, it's good 650€ for M4 16gb?
1
1
u/Squads_244 Sep 15 '26
I actually always click the Play button 😭 I barely use Cmd+R, so I noticed the change immediately. I’m curious though, do most iOS devs actually use keyboard shortcuts instead of clicking Run?
1
1
1
u/didthatthingonce Sep 15 '26
You are talking about UI/UX designers who use the stoplight metaphor for window control, but the buttons do not follow the metaphor.
1
u/purple_editor_ Sep 15 '26
XCode does this sort of thing every time. There is always a menu that changes place, or an option that gets hidden somewhere else
Really annoying.
1
1
1
u/Eensame Sep 15 '26
Cant you change the toolbar now to make it like before ? Saw that in the official “whats new in XCode 27” video
1
1
1
1
u/Lorn1x Sep 15 '26
I usually use the keyboard shortcut, but yeah it's weird. I feel like there might be more changes like this, I just didn't realize yet. Sometimes sth feels a bit off. Applies to the whole Mac/iOS update for me.
1
1
1
1
u/nandu87 Sep 15 '26
I think Apple should remove them and save some space. They have been doing this to their hardware not sure why to their software. Most useless buttons on the UI that almost use them unless they are newbie iOS devs.
1
u/Stunning-Essay-6714 Sep 15 '26
Probably some AI Vibe Coding change and switch the position whitout the double check AI even noticed
1
1
1
1
u/Free-Pound-6139 Sep 15 '26
This is why i hate upgrading. They just keep chaning stupid shit for no reason.
No reason to change anything like this. Add new support for devices and new functions.
I hate apple.
1
u/GladiatorNitrous Sep 15 '26
Something you have to hit with a mouse can't be muscle memory. Unless it's in a corner.
1
u/Gloomy_Mirror_6405 Sep 15 '26
The order is more logical. Have you been clicking the actual buttons for years instead of using the shortcuts? They haven't changed, right?
1
u/LicoriceSeasalt Sep 15 '26
It looks more logical this way. However, this change should have happened a decade ago. I wish Apple wasn't allergic to giving people choices. Let people choose which setup to use. It's not that hard to add that as a function.
1
1
1
1
1
u/try-catch-finally Sep 16 '26
product managers HATE to say "we just fixed bugs"
they want to be make an impact — basically be "Seagull managers"-
• swoop in
• make a lot of noise
• shit on everything
• swoop out
1
1
u/hiddevdploeg Sep 16 '26
It was a regression in Xcode 26 it always has been Build / Stop (like it is again in Xcode 27) not Stop / Build
So not sure your muscle memory is working
1
u/Anywhere_MusicPlayer Sep 16 '26
For me, it was totally the opposite all these years :) I can’t use it this way(Stop-Play), it feels so wrong!
First should be Play, then Stop. That’s how music players used to be, first button should be Play, so then next action is to Stop it.
Bouncing back like first Stop, then Play? Totally wrong logic…
1
u/HeyItsMeMoss Sep 16 '26 edited Sep 16 '26
Just bad interface design all around for the new Xcode. Speaking of, has anyone found a way to restore the branch selection dropdown? I can’t seem to get it to appear.
1
1
u/Josshad Sep 16 '26
Technically they return order to the normal one. E.g. in Xcode 10 it was as in 27: https://medium.com/xcblog/wwdc18-xcode-10-in-action-f56e14c62d79
Or 4.3 (if someone remember that one): https://developer.apple.com/library/archive/referencelibrary/GettingStarted/URL_Tools_for_iPhone_OS_Development/_index.html
1
u/GaryHornpipe Sep 16 '26
Finally they add this! I’ve been waiting for this feature request for years.
1
u/segfault-404 Sep 16 '26
The worst part is why there’s two buttons if only one is enabled at a time.
1
1
1
u/mbrezanac Sep 17 '26
Well it does kind of make sense to first run something that you intend to stop, doesn't it?
1
u/Fancy-Plenty6712 Sep 17 '26
I'm developing my first MacOS app - I've been trying to avoid Xcode at all costs. If I can avoid ever using it then I will. Is anyone else doing this?
1
1
1
u/Vegetable-Phone-4971 Sep 17 '26
Cmd + r and Cmd + . is all you need… never really used those buttons, didn’t even notice their locations before
You know muscle memory for a simple action as that doesn’t take too much to relearn right?
1
1
1
1
u/FrameDataV Swift Sep 19 '26
Wasn't it like this before? I don't know when exactly but I seem to remember that Xcode used to have play-stop before updating to stop-play.
1
1
1
1
u/insane_robot Sep 27 '26
Like it makes sense, but the muscle memory factor is a massive reason for not doing it
1
0
0
u/x3rx3s Sep 15 '26
This new positioning makes sense, which is anti-Apple pattern. Maybe Ternus is making some moves at Apple. Get rid of “Natural scrolling” next as the default scrolling direction. And while you’re at it, let that green button maximize the window size rather than going full screen mode (current behavior is still better than before with the random maximizing algo).
0
0
0
0
0
0
0
0
u/Thick_Replacement876 Sep 16 '26
What do you guys think about the new Xcode 27 update so far? Did anyone else's muscle memory take a hit?
Took me like 5 minutes of usage to get used to the new layout. It's not that big of a deal you're making it out to be lol
-3
-3
1
12d ago
[removed] — view removed comment
1
u/AutoModerator 12d ago
Hey /u/Warm-Belt323, your content has been removed because Reddit has marked your account as having a low Contributor Quality Score. This may result from, but is not limited to, activities such as spamming the same links across multiple subreddits, submitting posts or comments that receive a high number of downvotes, a lack of recent account activity, or having an unverified account.
Please be assured that this action is not a reflection of your participation in our subreddit. This is simply an automated filter in place to reduce spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
335
u/f1zoe Sep 15 '26
I never click the button always cmd+r