1
The Best of Figma This November
Mikuláš Žačok
Visual Content Creator
Extended collections + improved variables
- Added the ability to expand the design system into multiple “modes” (e.g., different brands) that are linked to the main system — when you change the base, the changes are automatically reflected in all extensions.
- Improved interface for editing variables: import/export variables as JSON, clear overview of all collections, the ability to create variables directly in groups, and the modal window now defaults to full-screen view.
- For Pro plans and above, it’s now possible to have more modes for variables: Pro → 10, Enterprise/Organization → 20 modes.
New products and features:
- Figma Sites (public beta): allows you to easily create websites, blogs, or portfolios with dynamic content (lists, pages connected to a CMS). Content can be quickly edited without changing the design.
- Figma Make: brings connectors to tools like Notion, Linear, Atlassian, GitHub, Monday.com, and more. Allows prototyping with real documents, tickets, etc.
- Within Make, it’s possible to test experimental AI models, such as “Gemini 3 Pro.”
Changes for developers – API + integrations
- If you have a plugin or app using the REST API, from November 17, 2025, you’ll need to re-publish OAuth applications with new required details (application owner, declared scopes).
- API usage limits have been updated (new rate limits).
You can find more information here.
2
React Native 0.82: New Architecture and Faster Development
The React Native 0.82 release is here, now running exclusively on the new architecture (the old one is no longer supported). This version brings faster app startups, more options for developers, and the experimental Hermes V1 engine. Core React has been updated to version 19.1.1, improving hooks and ref functionality. Android developers will appreciate the new debugOptimized build, which speeds up debugging.
What should you watch out for?
- Hermes V1 is still experimental — to try it out, you’ll need to build RN from source and set up a specific configuration.
- Check the compatibility of your libraries and plugins — some older packages may not yet support the new architecture or DOM‑API.
- After updating, previously hidden bugs may surface — for example, unhandled promises are now shown as errors in the console.
You can find more info here.
3
Angular v21 introduces highly anticipated features: signal forms, Angular Aria, AI enhancements, and the end of zone.js
Ján Hažinčák
Developer
Signal Forms
In addition to reactive and template-driven forms, Angular v21 introduces a new way to build forms — signal-based forms. This long-anticipated feature significantly simplifies working with forms by leveraging the same concepts developers already use with signals. At the core is the newform() function and the [field] directive, which let you bind a signal directly to your form model:
interface LoginData {
email: string;
password: string;
}
const loginModel = signal<LoginData>({
email: '',
password: '',
});
const loginForm = form(loginModel);
Usage in the view is simple:
<input type="email" [field]="loginForm.email" />
<input type="password" [field]="loginForm.password" />
Validation
Validation with signal forms is just as simple. Theform() function accepts a schemaOrOptions parameter, where you can declare validators:
const loginForm = form(loginModel, (schema) => {
debounce(schema.email, 500);
required(schema.email);
email(schema.email);
});
Signal forms represent a modern, simpler, and more transparent way to work with forms in Angular—and will likely become the preferred approach in the future.
Angular Aria
Another interesting addition is Angular Aria—an installable set of ready-made component patterns that provide built-in accessibility support. They include correct ARIA attributes, keyboard interactions, focus management, and are screen reader ready.
This is a great foundation for building custom UI libraries or atomic components, especially for larger projects where accessibility is a necessity.
Read more on the official Angular Aria page.
Vitest as the new official test runner
As mentioned in previous articles, Angular was looking for a new test runner. The community anticipated it would be Vitest—and Angular v21 has now confirmed it. Vitest is now the official default test runner for new Angular projects.
However, you can still use the deprecated Karma or Jasmine, even within a single project. For new applications, though, Vitest is the default.
Farewell to zone.js
After more than 10 years, Angular is officially dropping the requirement to include zone.js in projects. For years, this library was the foundation for Angular change detection—monitoring async processes in the browser and enabling automatic UI updates.
With the arrival of signals, this functionality is no longer needed. Angular now works reliably even without zone.js, resulting in notable improvements in performance, predictability, and the overall simplicity of the framework.
Angular MCP
Angular MCP, introduced in Angular 20.2, has been marked stable in version 21. MCP (Model Context Protocol) gives AI assistants in IDEs (e.g., VS Code) more context and structure for code generation.
The result is more precise, higher-quality, and contextually correct Angular solutions provided by tools that integrate AI.
Improvements in documentation, migrations, and other updates
Alongside the major updates, this release also brings plenty of smaller but practical improvements, such as:
- improved documentation for routing, DI, Angular Material customization, and Tailwind CSS integration,
- new migration commands for older projects (e.g., converting NgClass and NgStyle to modern class/style bindings),
- various other tooling and workflow optimizations.
There’s a lot to cover, so be sure to check the full official announcement.
4
Cursor 2.0 is changing the way software is developed
Lukáš Huňár
Developer
5
The EU launches an investigation into the cloud services market under the DMA
Matej Matfiak
špecialista na SAP CPI
- Easy switching between providers: customers should be able to move to another service without complications or high costs.
- Equal conditions for smaller providers: large companies must not disadvantage or block the growth of smaller firms.
- Service transparency: prices, terms, and availability of services must be clear and understandable.
Missed the latest edition of Coder’s Corner? Read it here.