Apple now requires iOS and iPadOS apps uploaded to App Store Connect to target iOS 13 or later, a rule in effect since September 9, 2026. Apple’s submission page adds that starting April 2027, iOS and iPadOS apps must be built with the iOS & iPadOS 27 SDK or later and target iOS 15 or […]
Xcode 27 includes Swift 6.4 and SDKs for iOS 27, iPadOS 27, tvOS 27, watchOS 27, macOS 27, and visionOS 27. Xcode 27 supports on-device debugging in iOS 17 and later, tvOS 17 and later, watchOS 10 and later, and visionOS. Xcode 27 requires a Mac running macOS Tahoe 26.6 or later.
Building with Xcode 27 doesn’t work because of some intransparent XCStrings error… and I even can’t check with Xcode 26 anymore because Apple decided to not let me run it on macOS 27…
Isso porque, a princípio, haverá muitos apps que não aproveitarão o novo tamanho de tela caso sejam antigos ou se os desenvolvedores tiverem optado por não seguir as diretrizes da Apple.
Na prática, as versões atuais dos aplicativos serão exibidas em tela cheia na parte frontal e em tela quase cheia na tela interna. No primeiro vídeo publicado pela empresa, por exemplo, ela demonstra que os aplicativos serão alinhados à esquerda para ocupar a maior parte da tela, evitando a área da câmera.
Eis os demais vídeos compartilhados pela empresa:
Ao recompilarem seus aplicativos usando o Xcode 27.1, que será disponibilizado ainda neste mês, os desenvolvedores passarão a contar com controles mais precisos. Seus aplicativos poderão aproveitar toda a largura da tela interna, além de incluir um módulo de pré-visualização que exibe como os apps ficarão nos quatro layouts — fechado em modo retrato, fechado em modo paisagem, aberto na horizontal (paisagem) e aberto na vertical (retrato).
Bezels dos iPhones 18 Pro/18 Pro Max e do iPhone Duo
Por fim, a empresa realizará os chamados iPhone Duo Group Labs, laboratórios que permitem aos desenvolvedores se juntar aos engenheiros e designers da Apple — de forma online — para fazer perguntas e obter orientações.
Microsoft has released Visual Studio Code 1.136, an update to the popular programming editor that previews an Agent Merge feature and introduces two experimental features for agentic coding.
Agent Merge, a preview feature, helps take a pull request across the finish line, Microsoft said. Agent Merge asks an agent to address review feedback, fix failed checks and merge conflicts, and rerun workflows until the pull request is ready to merge. To use Agent Merge, turn on the setting chat.agentMerge.enabled. Then you can enable Agent Merge for a session by running “Enable Agent Merge for Active Session” from the Agents window or selecting the “Agent Merge” button in the title bar.
VS Code 1.136 also introduces multi-root workspaces, an experimental feature that allows developers to work with GitHub Copilot and Claude agents across multiple project folders in the editor window chat view. Agent hooks remain scoped to a single workspace folder, Microsoft said. If hooks are detected in multiple folders, VS Code prompts the user to select the primary folder from which to load them.
Another experimental feature in VS Code 1.136 is chat backgrounds in the Agents window. This allows users to personalize the Agents window with a theme-aware pattern of built-in VS Code icons or an image of their own. Also new for chat are enterprise controls for dictation data. The new controls allow administrators to manage the dictation model and language-model transcript cleanup through enterprise policies. Microsoft said it was possible to require on-device transcription and disable language-model cleanup, so dictation remains available while preventing dictation data from being sent to cloud transcription or a Copilot model.
As those new models start shipping on 22 September, the window for the first public release of Golden Gate has narrowed to 15-22 September, with greatest likelihood on the same day as the arrival of those new Macs.
[…]
At the same time as the release of Golden Gate, we should get Tahoe 26.7 and Sequoia 15.8, but it looks increasingly likely that the final version of Sonoma has been 14.8.9, released on 6 August.
As we prepare to flee from the visual horrors of macOS Tahoe at last, this article is a reminder that it wasn’t the first major release of macOS that has had blatant bugs in its interface, although I suspect it may be unique in that those were intentional. While progress in Golden Gate has been limited, I hope you’ll find it rectifies some of the worst errors of Liquid Glass.
Many Macs will be left behind, as Golden Gate drops support for Intel.
Normally, I update around January. With Tahoe I waited until July. This time, I’m considering updating to Golden Gate soon after its release. The downside is that Xcode 26 doesn’t run on Golden Gate, so I would have to drop support for many older macOS versions (about 3% of my customers’ Macs). But it seems like Apple’s going to force that soon, anyway, as one of the next Xcode 27 updates will likely drop support for Tahoe. I want to get off Xcode 26, both to use the newer SDK and because there are various debugging/testing things that don’t work properly.
I am working on a new app. Right now, I am targeting back to macOS Sequoia. I think that would be a good OS to target but becoming quite old with Golden Gate just around the corner. […] I wonder if I should just target macOS Golden Gate and focus testing on that.
i’m in the exact same boat. i’d really like to stay on macOS 15 and whatever Xcode works there. it means i can still build things in the old UI and mostly Tahoe and GG respect it.
but recent bug reports from beta testers and the inability to see these bugs on my VM has made me feel very stuck here — like apple has purposefully made it difficult to move forward and support older versions too.
I don’t appreciate being forced by Xcode 27 to drop support for macOS 10.13-11.0. It’s my decision which OSes I want to support, not Apple’s. Yes, I can keep Xcode 26 around until submissions require Xcode 27, but what then?
Originally, Xcode 27 was documented as supporting Big Sur on Intel Macs, but now the earliest is Monterey.
I’m frustrated, too, but it’s more honest than the recent releases that claimed to support deployment on older macOS versions when Apple clearly hadn’t tested that it actually worked. I filed bugs, and Apple kept responding that they’d fixed it, when they hadn’t.
Using old versions of Xcode isn’t a great solution because they aren’t supported on Golden Gate. Swift also makes it more difficult to call newer APIs when using an older SDK. You can’t just copy/paste a method prototype or constant value and conditionally use it when running on a newer OS.
I eventually found a hidden workaround that changes the errors back into warnings. That is good news, but it does not make the concern disappear. The setting is undocumented, absent from the normal Xcode interface, and currently being tested only in a beta toolchain. The larger question is what Apple intends to enforce when Xcode 27 is final and, later, when App Store submission requirements move to its SDKs.
[…]
Apple’s current Xcode system requirements list Xcode 26 with deployment targets beginning at iOS 15 and macOS 11. Yet developers have been able to enter older targets manually. In an Apple Developer Forums discussion about Xcode 26, an Apple product manager explained that the published deployment target range is aligned with simulator support and on-device debugging. The accepted answer confirms that an iOS 13 target can still build even though it falls below the range in Apple’s table.
My own tests went further. Xcode 26.5 compiled a project targeting iOS 9.0. It warned that the target was older than the supported range, but the build succeeded. On macOS, I have compiled current apps with deployment targets as old as macOS 10.9. Xcode warned me, but it still produced working applications.
[…]
For iOS and iPadOS, staying on Xcode 26 is not a lasting option. Apple has repeatedly made a current Xcode and SDK mandatory for new App Store submissions. […] If any one of those conditions fails, iOS and iPadOS developers will have no normal App Store path for publishing new updates that still support versions older than 15.
Just want to remind you guys that if you move to Xcode 27, the only “officially” supported and sanction Xcode for GG, UIDesignRequiresCompatibility is no longer respected across the 27 OSes (apps built with older Xcodes still are). So you might suddenly find out you have a lot of work ahead of you, adding support for the dreaded Glass. And 27 Glass is not the same as 26 Glass. That can be an issue if you skipped 26 altogether but still want to support it.
I mostly ignored the Xcode 27 betas (mainly due to the barely-usable Device Hub) so I didn’t realize the passive-aggressive prompts to drop support for iOS < 15 that you get when submitting apps is being backed up by Xcode 27 refusing to compile apps at all unless you bump the deployment target 😧
Adam Engst looks back at HyperCard as an early tool that democratized software creation, then connects its legacy to today’s AI-assisted development. He outlines how Claude helped turn an idea for tracking macOS setting changes into a working Mac app, SetShot. Adam discusses Xcode, GitHub, rapid iteration, and the value of visual feedback in his development process, and how AI lowers programming barriers without eliminating the need for thought, judgment, and effort.
The genetic code is what life everywhere uses to convert the information contained in DNA into specific protein sequences. With minor variations, the same genetic code is used by every living thing on Earth, suggesting it was already present in the last common ancestor of all of them. It's not an easy thing to change, because so many things in every cell depend on it.
Nevertheless, some preliminary steps have been taken. Researchers have managed to add some new amino acids to a bacterial cell and were able to make proteins that were one amino acid less than usual. But it's a slog; for some of this work, people have had to re-engineer every single gene in a bacterial genome.
Now, researchers have found a way to operate two separate genetic codes simultaneously, avoiding the need to do any work to compensate for altering the code that every protein in a cell relies on. They didn't test it in an actual cell, and it might cause some problems there. But it's a creative solution that should accelerate some synthetic biology work.
Have you ever suspected macOS of silently changing your settings during an update? Adam Engst’s free SetShot captures and compares snapshots of your Mac’s configuration so you can catch those changes—and maintain a journal of your own customizations.
The core Unicode algorithms (normalization, casing, bidi, collation) are deliberately bounded, but UTS #35 transliteration rules, under their natural unbounded semantics, are not. This is a result I haven’t found published before.
These rules ship as locale data in ICU, the Unicode library shipped in operating systems, browsers, runtimes, and databases. Whether a given rule file terminates on a given input is undecidable.
Mike Schmitz previews his Road to Macstock session on starting a YouTube channel in 90 minutes, emphasizing creativity, repetition, audience connection, and practical tools over perfection. Mike discusses handling harsh comments, finding personal value in publishing, and using AI thoughtfully as a creative partner. His goal is to help get anyone on YouTube that wants to be there.
Only a few hours after Apple’s WWDC keynote, members of the MacPaw leadership team sat down for a conversation about Apple Intelligence, and Siri’s renewed promise. Topics touched on included privacy, developer access to user context, hybrid AI processing, Setapp’s role, and how AI is reshaping app creation, customer support, and software strategy. Participants included Oleksandr Kosovan, Founder and CEO?, Sergii Kryvoblotskyi, Director of AI and Research, Dmytro Melnyk, Chief Product Officer and Grant Belaire, Chief Marketing Officer.
At NAB 2026, Chuck Joiner talks with Ryan Burke, Portfolio Director for RØDE about the new RodeLink 2 UHF wireless system, developed with Lectrosonics expertise. The discussion covers interference-resistant UHF performance, 32-bit float recording, timecode, adaptive power, battery life, and removable storage media. Ryan also provided a look at the new RODECaster Studio AI audio editing app for podcasters.
On the show floor at NAB in Las Vegas, Jim Tierney of Digital Anarchy discusses ShotNotes, a Premiere Pro panel that keeps project notes, time codes, links, timers, and collaboration details inside the edit instead of scattered across documents or sticky notes. He also previews Beauty Box Video AI development and explains where generative AI can help video pros, where traditional AI still shines, and why AI is useful but not a magic bullet.
Começando pela primeira novidade supracitada, ela permite que o Claude envie informações de uma sessão para outra num mesmo computador ou responda a sessões em outras máquinas — algo que pode ser bastante útil quando mais de uma sessão está trabalhando num mesmo projeto.
O recurso pode ser usado, por exemplo, quando há uma mudança que quebra o sistema como um todo e cuja resolução depende de algo executado em outra sessão — ou simplesmente quando alguma delas precisa saber de uma decisão de design ou de um resultado de testes.
Por ora, no entanto, apenas texto simples é suportado, de modo que nenhum arquivo ou o histórico da conversa é transferido entre as diferentes sessões. Uma sessão também não pode aprovar comandos originados de outras sozinha — sempre é requerida a autorização do usuário para tal.
New in Claude Code: your sessions can now message each other.
Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task. pic.twitter.com/PtNsfXeQXP
Novidade no Claude Code: agora suas sessões podem trocar mensagens.
Em vez de ter que se explicar novamente em outra sessão, agora você pode pedir ao Claude para fazer isso. Ele envia um resumo (não seu histórico ou arquivos), e a outra sessão o recebe durante a execução da tarefa.
O Claude pode decidir enviar uma mensagem por conta própria se julgar necessário, ou o usuário pode solicitar explicitamente que ele informe algo a outra sessão — inclusive, é possível definir se elas devem ser aceitas ou recusadas automaticamente ou se devem requerer aprovação.
Modo automático como padrão
Um dos recursos mais interessantes do Claude Code é o modo automático, que permite à plataforma usar uma espécie de “classificador de segurança” para decidir se prossegue ou não com determinada tarefa, sem precisar a todo instante solicitar a permissão do usuário.
Com o modo automático, que antes era opcional, o Claude pode trabalhar sozinho por períodos muito mais longos e sem qualquer interferência humana — o que permite que seus modelos realizem tarefas complexas durante horas e entreguem um trabalho mais completo ao fim da sessão.
Pesquisas feitas pela Anthropic indicaram que o modo automático também tende a deixar o desenvolvimento mais seguro, já que desenvolvedores costumam aprovar 97% dos pedidos de permissão por reflexo (sem revisão), e bloqueiam bem menos prompts perigosos que a ferramenta (acima).
Com isso, esse modo agora passará a ser o modo padrão do Claude Code nos planos Pro, Max e Team — a partir de 14 de agosto. Como consequência dessa mudança, a Anthropic também deixará de cobrar dos usuários desses planos pelo custo computacional desse classificador.
Bending Spoons has snapped up Airtable to add to its portfolio of software companies, alongside AOL, Evernote, WeTransfer, Brightcove and Vimeo
Airtable made its name as a builder of low/no code database services, aimed particularly at non-technical staff, but is now one of many vendors facing financial difficulties in the face of the SaaS/AIpocalypse. The arrival of AI coding tools, which offer non-technical employees more flexible ways to build business applications, has hit demand for its services.
Bending Spoons bought Airtable in a deal it valued at just $1.285 billion, a far cry from the $11.7 billion Airtable was worth at its peak.
Bending Spoons has built its portfolio by buying once-successful companies like Airtable that have struggled to cope with newer, nimbler competitors or failed to adapt to emerging technologies. Bending Spoons takes these companies, cuts costs and markets them aggressively with the goal of returning them to profitability.
“Airtable is a pioneering brand reshaping how teams organize data and manage critical workflows. We’re committed to investing in Airtable for the long run, and doubling down on its core strength: bringing teams and workflows together in one flexible workspace. We plan to expand what can be done across the full spectrum of work and make Airtable even more valuable to customers at every scale,” said Luca Ferrari, Bending Spoons CEO and co-founder.
Login
