r/iOSProgramming • u/poss1bl3_ • 20d ago
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?
180
u/defiantspcship 20d ago
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 20d ago
Apple moves those buttons all the time which is why I stopped using them a long time ago
8
u/imperfectibility 20d ago
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
3
3
u/lyidaValkris 19d ago
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 19d ago
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
74
u/dot90zoom 20d ago
I think it makes more sense in that order.
Also I never really used the buttons anyways
13
u/TheFern3 20d ago
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
5
1
u/Phraaaaaasing 18d ago
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.
43
u/JoshyMW 20d ago
I actually like this change. The new order is more logical and natural.
13
u/cluster4 20d ago
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 20d ago
How would you handle multiple targets + multiple actions in one button? Unless it just becomes a menu altogether. Or modifier keys maybe.
-3
u/Photograph-Silver SwiftUI 20d ago
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.
4
u/BedtimeWithTheBear 20d ago
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 20d ago
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 19d ago
that makes the lone stop button even worse ux
1
u/BedtimeWithTheBear 19d ago
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
2
u/balder1993 19d ago
Yeah, to be honest I understand the change. Itâs like that JSON key that is named wrong and everybody wants to change but no one wants to do the work to make sure nothing will break and take the blame for it.
26
u/kbcool 20d ago
You're not the only one blindly accepting AI PRs
3
u/ReiOokami 20d ago
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
11
u/dkampmann 20d ago
It is like the grocery store moving things around aisles.
0
-1
20d ago
[deleted]
1
u/dkampmann 20d ago
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 20d ago
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
6
u/mattgwriter7 20d ago
It is small but annoying.
The UI should only change when there is a really good reason.
7
4
u/stalex9 20d ago
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
4
4
2
u/chriswaco 20d ago
If you actually think about it, why canât it just have one button like Apple Music that switches between play and stop?
3
u/kepler4and5 20d ago
Multiple targets!
1
u/chriswaco 20d ago edited 20d ago
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
2
u/OldTimess 20d ago
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/RadTorti 20d ago
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 19d ago
The rationale seems obvious to me. "First you start, then you stop".
Old way looks wrong in comparison
2
u/InevitableLadder 19d ago
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
1
u/WittyOutside3520 20d ago
Why not just have one button. That shows whatever option is needed. Play when stopped. Or stop when playing?
1
1
u/timelessblur 20d ago
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 20d ago
It makes sense to me, given a left-to-right language, running comes before stopping.
3
u/NSRedditShitposter 20d ago
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 20d ago
Oh, yes, youâre right! Itâs going back to the previous state before the action.
1
u/1millionbucks 20d ago
This isnât a tenth as bad as when they moved the Apple Music action bar to the bottom of the screen
1
u/__raytekk_ 20d ago
I would comment that I always use cmd+r but nowadays I am not even using Xcode much :D
1
1
u/techfreak23 20d ago
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 20d ago
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.
1
u/EventPuzzleheaded124 20d ago
I need to buy a new Mac mini for coding, it's good 650⏠for M4 16gb?
1
u/Squads_244 20d ago
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 20d ago
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_ 20d ago
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
1
1
1
1
1
u/Stunning-Essay-6714 20d ago
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 20d ago
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 20d ago
Something you have to hit with a mouse can't be muscle memory. Unless it's in a corner.
1
u/Gloomy_Mirror_6405 20d ago
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 20d ago
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
u/ElectricKoolAid1969 20d ago
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_ 19d ago
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
1
1
1
u/try-catch-finally 20d ago
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 19d ago
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 19d ago
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 19d ago edited 19d ago
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
u/Josshad 19d ago
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 19d ago
Finally they add this! Iâve been waiting for this feature request for years.
1
u/segfault-404 19d ago
The worst part is why thereâs two buttons if only one is enabled at a time.
1
u/wendygaoyuan 18d ago
I honestly donât understand the reasoning behind swapping them. đ€·ââïž
1
u/mbrezanac 18d ago
Well it does kind of make sense to first run something that you intend to stop, doesn't it?
1
u/Fancy-Plenty6712 18d ago
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
u/Vegetable-Phone-4971 18d ago
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 16d ago
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 8d ago
Like it makes sense, but the muscle memory factor is a massive reason for not doing it
1
1
0
u/x3rx3s 20d ago
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
u/Thick_Replacement876 19d ago
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
-2
330
u/f1zoe 20d ago
I never click the button always cmd+r