iOS | Techlist.io

discordFeb 26, 20253 min readCurated summary

Discord Patch Notes: October 1, 2024

Discord’s October 1, 2024 patch focuses on mobile performance, storage efficiency, usability improvements, and broad bug fixes. Android users should see smoother chat rendering and lower resource usage, while iOS users may benefit from substantially reduced data storage. The update also introduces desktop Soundboard improvements, macOS screen-sharing refinements, and Animated WebP support. ## Mobile Performance and Storage - Android chat rendering improvements reduced slow frames by up to 60%, depending on the device. - Android chat-list memory usage fell by approximately 12%, making scrolling through message histories smoother. - Mobile server-list virtualization keeps only visible servers loaded: - Memory usage improved by 14% for users in many servers. - CPU usage improved by 25%. - Mobile unread indicators now consistently appear above the correct message, even with many unread messages. - iOS data-store changes reduced storage usage for the most affected 1% of users from 5.7 GB to 1.7 GB. - Fixed iOS message search results beyond the first page and crashes involving certain NFC hardware keys. - Resolved tablet orientation-detection issues and several Android problems involving read states and mobile keyboards. ## New Features and Interface Updates - macOS screen-sharing startup now has a more consistent and streamlined interface. - Desktop received a redesigned Soundboard interface for easier sound navigation and interaction. - Web and desktop clients can now play Animated WebP attachments, offering smoother playback and potentially lower bandwidth usage. - Electron was upgraded to version 32, with expected incremental performance and crash-reduction benefits. - Pasting a URL over an existing link now properly replaces the original URL instead of creating unexpected Markdown behavior. - Activity Status now correctly displays PS5 games. - The green acceptance check mark has returned to friend-request notifications. ## Interface and Navigation Fixes - Corrected visual issues involving emoji pickers, GIF categories, profile status bubbles, avatar decorations, fonts, borders, and themed search filters. - Fixed navigation problems in GIF categories, the Shop, Friends UI, mutual-friend lists, and profile popouts. - Improved accessibility and navigation indicators so they are no longer cut off in several profile and list views. - Corrected layout issues in Student Hub, channel settings, server settings, Notification Center, and message requests. - Fixed Quests links, Server Guide icons, role expansion behavior, and the display of permission descriptions on mobile. - Restored functionality for the Toggle Overlay hotkey after switching applications with Alt-Tab. - Corrected several modal and popup layering issues, including stickers, Soundboard uploads, and quest cards. ## Reliability and Content Fixes - Fixed crashes when viewing deleted channels in Audit Log with ModView open. - Corrected poll countdown text as polls approach closure. - Member verification and rules-agreement indicators now reflect the correct state. - Fixed incorrect game-presence names appearing in Japanese. - Resolved issues with rate-limited or frozen GIF categories. - Corrected timeout duration display in moderation views. - Fixed profile customizations failing to load on the first Shop attempt. ## Chat Improvements - Fixed mobile chat layout issues, including the missing “Jump to Bottom” button and overlapping composer elements. - Android web embeds now scale correctly instead of cutting off image content. - Corrected message-height calculations and action-sheet handle placement. - Prevented Avatar Decorations from being clipped at the top of chat. Discord’s update is primarily a reliability and performance release. Users—especially those on Android, iOS, or with many servers—should benefit from smoother navigation, lower resource consumption, and fewer interface defects as the changes roll out across platforms.

Read original

iOS Android Markdown Macos+4

discordFeb 26, 20253 min readCurated summary

Discord Patch Notes: November 1, 2024

Discord’s November 1, 2024 patch focuses on improving performance, reliability, responsiveness, and cross-device usability. Major updates include stronger foldable-device support, better mobile multitasking and side-by-side views, macOS screen-sharing keybinds, and website performance gains of up to four seconds in average page-load time. The release also fixes a broad range of interface, messaging, theming, and platform-specific bugs. ## Foldable Devices and Multitasking - Foldable devices receive improved support designed to work more reliably without bespoke fixes. - Mobile Discord now handles resizing more intelligently for Sidecar, split-screen, and other multitasking layouts. - Users are encouraged to report remaining foldable-device issues through Discord’s bug megathread or support tickets. ## Desktop and Web Performance - Electron was upgraded from version 30 to version 32 on Windows, macOS, and Linux. - Discord.com received performance improvements that reduce average page-load times by up to four seconds. - Additional core web vitals and responsiveness were improved. - macOS 15 and later now support a keybind for toggling screen sharing, available under **User Settings > Keybinds**. - Friend links opened in a browser now properly communicate with the running desktop client. ## General Interface and Platform Fixes - Fixed missing profile-screen actions, incorrect profile banner zoom, navigation-bar rendering issues, and mobile layout shifts. - Corrected avatar decoration overlap with unread-message status indicators. - Fixed notification bubble shapes, emoji-picker category navigation, theme colors, keybinding icon colors, and long category-name handling. - Improved profile banners and Server Guide text rendering on foldable devices and iOS. - Fixed issues involving onboarding prompts, the App Launcher, Mod View, channel permissions, and role assignment through Simplified Profiles. - Corrected Shop problems involving banners, scrolling, collection tile shapes, and app-button icon colors. - Poll answers can now be selected and copied. - Fixed overlay custom-emoji visibility, profile-effect controls, Nitro gifting padding, and collectible purchase wording. - X.com embeds no longer incorrectly interpret embed content as Markdown. - Fixed several mobile and desktop rendering problems, including channel settings flashes, emoji alignment, and profile layout behavior. ## Chat and Messaging - Corrected oversized emoji rendering in chat. - Fixed mobile Voice Message tooltips, input placement, and animation behavior. - Deleted messages should no longer briefly remain in mobile DM previews. - Fixed an iOS issue where drafts persisted between channels and another where text scaling changed after the keyboard collapsed. - Users can open profiles by clicking names in reply previews. - Prevented rapidly renaming a newly created thread from creating duplicate threads. - Fixed thread-creation theming issues and swipe actions during chat animations. - Corrected mobile notification settings appearing incorrectly in DMs. - Fixed iOS emoji alignment problems in messages. Overall, the patch is primarily a quality-of-life release: users should see better performance across web and mobile, more dependable support for foldables and multitasking, and fewer visual and interaction bugs.

Read original

iOS Android Performance Optimization Linux+4

discordFeb 26, 20252 min readCurated summary

Discord Update: December 19, 2024 Changelog

Discord’s December 19, 2024 changelog recaps the year’s most useful performance and reliability improvements through a festive poem. The updates focused on making mobile apps more stable and responsive, speeding up servers, GIFs, chat, and APIs, and improving image quality and storage usage. Discord concludes by encouraging users to join voice, play games, or Go Live, while promoting Nitro gifting. ## Mobile Stability and Performance - iOS crash fixes reduced the overall crash rate by **84%**. - Android’s chat renderer reduced slow frames by up to **60%** and lowered chat-list memory usage by about **12%**. - The Android Expression Picker—covering emojis, GIFs, and stickers—saw up to **50% fewer dropped frames** and approximately **7.5% lower memory usage**. - Foldable-device support and multitasking were significantly improved. - Mobile server lists were virtualized so only visible servers remain loaded, improving scrolling performance. - Server switching on Android and iOS became more than **30% faster**. - Mobile GIF Picker loading times improved by up to **80%**. ## Backend and Media Improvements - Infrastructure changes, including moving to Google Cloud C3 instances and removing an Nginx layer, reduced p90+ API latency by roughly **25%**. - Discord’s media proxy now preserves ICC color-profile data when resizing images into WebP, improving color accuracy across platforms. - iOS data-storage changes reduced disk usage substantially; the most affected 1% of users went from approximately **5.7 GB to 1.7 GB**, with some users recovering up to **4 GB**. ## Seasonal Extras - The recap is presented as a “Fixmas” poem summarizing fixes from Discord’s 2024 Patch Notes. - Users who gift Nitro during the promotion also receive an Avatar Decoration. Together, these changes show Discord’s emphasis on incremental improvements that make everyday communication faster, more reliable, and less demanding on mobile devices.

Read original

iOS Android API Performance Optimization+4

discordFeb 26, 2025Original article

Discord Update: September 26, 2024 Changelog (opens in new tab)

Discord’s September 2024 update centers on transforming the platform into a more interactive entertainment hub while significantly hardening its security infrastructure. By centralizing third-party integrations through a new App Launcher and implementing end-to-end encryption for audio and video, the platform aims to balance expanded developer functionality with robust user privacy. ### The App Launcher and Interactive Activities * The newly launched App Launcher is now available across desktop and mobile, allowing users to search, browse curated collections, and add thousands of apps directly to their accounts for use in chats and voice calls. * Four new Activities have been integrated: *Arena Kingdoms* for cross-server battles, *Echo Chess* for daily puzzles, the Viking-themed *Battletabs*, and the social-focused *Magic Circle*. * New image-editing capabilities allow users to hover over chat images to access the App Launcher for quick modifications, such as adding captions or using Viggle’s “Animate” command to generate motion from static photos. * The developer ecosystem has been expanded to allow third parties to build, launch, and monetize their own Activities, with options to opt-in to platform-wide discovery via the launcher. ### Security and Privacy Enhancements * End-to-End Encryption (E2EE) is being introduced for all audio and video communication, including DMs, Group DMs, voice channels, and Go Live streams, ensuring that stream data is accessible only to participants. * Support for Passkeys has been implemented, allowing users to replace traditional passwords with biometric authentication such as Face ID or Touch ID. * Passkey technology remains localized to the user's device, ensuring that Discord does not have access to sensitive biometric data. ### Platform Performance and Community Resources * Discord’s engineering team reported a significant performance milestone, reducing iOS application crashes by 84%. * The "Discord Dojo" initiative has launched to provide educational content, including videos and blogs focused on message formatting and advanced keybinds for power users. * A new partnership with *Street Fighter 6* introduces themed shop items and a specific Quest that rewards users with a "Battle Field" decoration for their profiles. To maintain the highest level of account safety, users should consider migrating to Passkeys and verifying the encryption status during their next voice or video call. For those looking to increase engagement within their servers, the App Launcher provides a low-friction way to introduce collaborative games and media tools directly into existing conversations.

iOS Performance Optimization End To End Encryption Passkeys+3

figmaAug 30, 20233 min readCurated summary

How Spotify’s Design System Goes Beyond Platforms | Figma Blog

Spotify’s expansion to 45 platforms and more than 2,000 device types exposed inconsistencies between its product experiences. The company evolved Encore from separate mobile and web systems into a cross-platform design system focused on shared foundations and reusable components. Its goal is to make Spotify feel coherent everywhere without erasing the distinctive strengths of each platform. ## The Challenge of Consistency at Scale - Spotify’s 2019 ubiquity strategy aimed to make audio available across TVs, cars, computers, phones, and many other devices. - The design team needed more than broad platform coverage: users should recognize the experience as distinctly Spotify wherever they use it. - Components became central to achieving this consistency, from defining their scope to implementing them across products. ## The Birth and Evolution of Encore - When introduced in 2019, Encore had two main subsystems: - **Encore Consumer Mobile**, a flexible catalog of mobile-focused UI components. - **Encore Web**, supporting a wider range of web products. - Both systems used shared design tokens for foundational decisions such as colors and typography. - Over time, differences in component sizing, typography, and state treatments revealed that the subsystems needed greater commonality. - By 2022, flexibility had created too much divergence, prompting Spotify to rebalance the system toward reusable, consistent components. ## A Shared Layer Between Foundation and Products - Spotify created a specialized team focused on reusable components for Encore Mobile. - This new layer sits between the foundational system and Encore Consumer Mobile. - It acts as a “first line of defense,” reducing the need for product-specific teams to build every component themselves. - Developed in collaboration with Encore Web, the layer establishes platform parity from the beginning rather than retrofitting consistency later. ## Designing Components Across Platforms - The overall workflow remained familiar: research, design, and development. - The major change was coordinating design work across iOS, Android, and Web instead of designing for one platform in isolation. - Components are intended to share a coherent visual and behavioral language while still adapting to platform-specific requirements. - This requires collaboration among specialists, since web and mobile designers bring different domain expertise. - Spotify begins by bringing platform teams together and researching each platform’s unique characteristics before creating the shared component. Spotify’s approach treats a design system as more than a collection of platform-specific libraries. By establishing shared components early and combining them with platform-aware design, teams can create experiences that feel unified without sacrificing the qualities that make each device and interface effective.

Read original

iOS Design Systems Android Design Tokens+3

figmaOct 12, 20222 min readCurated summary

How we use data | Figma Blog

Figma uses data in two broad ways: functional data to provide its service and analytics data to improve the product. The company emphasizes collecting only the information necessary to operate Figma, while using aggregated usage insights and experiments to guide product decisions. Examples include improving file sharing and identifying performance problems in the iOS app. ## Functional Data - Functional data supports core account and product operations. - Figma collects a relatively small amount of information at signup: - Email address - Name - Role - This information enables usernames, password-reset messages, file creation, and collaboration. - Figma generally does not require sensitive information such as identity documents or verification. - Payment information for paid plans is collected and processed by Stripe. ## Analytics Data - Analytics data describes how users access and use Figma. - It helps teams understand: - Which features users adopt - Which features they ignore - Where users encounter difficulties - How usage varies across platforms - Data scientists analyze these signals alongside user research, product intuition, and direct feedback. ## Improving Features Through Experiments - A/B testing is a central part of Figma’s product-development process. - Experiments test hypotheses and measure how proposed changes affect user behavior. - In one study, Figma examined its file-sharing modal, where users invite collaborators, manage permissions, and publish work. - Research showed that: - Only 20% of users opened the share modal during their first month. - Only half of those users successfully shared a file. - Figma simplified the interface and moved secondary functions into separate tabs. - The change produced: - A 2% increase in users sending invitations - A 2% increase in users invited to each file - No observed decline in users publishing work to Figma Community ## Identifying Performance Issues - Figma uses data to monitor application performance across platforms and prioritize improvements. - After launching the beta iOS app, the data team analyzed crashes by platform, scenario, and timing. - The analysis found that prototypes were a major source of iOS crashes. - About 25% of prototype crashes occurred within the first 10 seconds of loading. Figma’s approach combines minimal functional data collection with analytics, experimentation, and performance monitoring. The practical goal is to use data selectively to improve usability, reliability, and collaboration while limiting the amount of sensitive information required from users.

Read original

iOS Data Science A B Testing Data Analytics+2

figmaMar 14, 20222 min readCurated summary

FigJam for iPad: space to explore and ideate | Figma Blog

FigJam for iPad was introduced to make brainstorming and collaboration more fluid across devices. The article argues that tablets’ focused, tactile nature complements FigJam’s infinite canvas, especially for sketching, exploring early ideas, and giving visual feedback. Although the standalone iPad app is being retired in 2026, FigJam remains available through the Figma app and the web. ## Why Tablets Suit FigJam - Desktop workflows often interrupt creative focus with notifications and constant context switching. - Tablets provide a more focused, single-app environment. - The iPad’s portability and touch or pen input make it feel similar to working in a notebook. - FigJam’s open canvas naturally supports freeform drawing, doodling, annotations, and low-fidelity exploration. - Users can move fluidly between desktop and tablet depending on the task. ## Embracing Early Ideas - Low-fidelity sketches make nonlinear exploration and iteration easier. - Rough ideas encourage collaboration rather than inviting narrow critique. - Users can sketch concepts on an iPad, then continue refining or sharing them from a laptop. - Team members can draw directly over one another’s ideas, making ideation more interactive. ## Making Feedback More Personal - Handwritten annotations can complement or replace traditional comments. - Users can circle, underline, and mark up text, diagrams, and sketches directly on the canvas. - Visual and handwritten feedback creates a warmer, more collaborative experience than written critique alone. ## Running Collaborative Sessions - The iPad can support group workshops as well as individual work. - Facilitators can display a FigJam file on a desktop screen while using the iPad for live annotations. - Quick actions—such as circling stickies or highlighting contributions—make meetings feel more natural and fluid. Figma positioned FigJam for iPad as an early step toward richer tablet-based design workflows. For current users, FigJam is available through the Figma mobile app or the web; the standalone iPad app is scheduled for retirement on January 8, 2026.

Read original

iOS Figma Figjam Android+3

figmaDec 15, 20212 min readCurated summary

What’s new in Figma: December 2021 | Figma Blog

Figma’s December 2021 updates focus on making collaboration and creation more seamless across Figma and FigJam. The release adds richer media support, improved drawing tools, and expanded mobile capabilities. Together, these changes help teams share context, refine ideas, and preview designs without interrupting their workflow. ## Enriching FigJam collaboration - Users can paste links into FigJam to watch Vimeo videos, play Spotify music, and share other rich media. - The new Vimeo plugin supports screen and webcam recordings directly within Figma and FigJam. - Recordings can be used for status updates, product demos, tutorials, and asynchronous collaboration. ## Highlighting and refining ideas - The new **Highlighter** tool emphasizes text and other FigJam elements. - Holding **Shift** while highlighting creates perfectly straight lines. - The **Eraser** tool removes individual strokes, making it easier to correct sketches and refine work in progress. ## Expanding mobile design workflows The updated Figma mobile app lets designers preview, review, and manage work more independently from a desktop. - Play prototypes directly on mobile devices. - Toggle hotspot hints during prototype playback. - Mirror selected desktop frames to a mobile device. - Share, browse, and view Figma files and prototypes. - Share, browse, and view FigJam files. - Navigate teams, projects, and workspaces from the app. - Updates are available for iOS and Android phones and tablets. Figma’s December release is primarily about removing friction from collaboration: teams can communicate with richer media, improve FigJam ideation with more precise tools, and validate mobile experiences directly on their devices.

Read original

iOS Figma Prototyping Figjam+4

figmaApr 2, 20182 min readCurated summary

Desperately seeking squircles | Figma Blog

Figma engineer Daniel Furse describes the search for an accurate mathematical model of Apple’s iOS “squircle” shape. The project illustrates Charles Eames’s idea that good design depends on recognizing and working enthusiastically within constraints. Although a superellipse initially appeared to be the answer, careful comparison showed that it was only an approximation, prompting further investigation into Bézier-based constructions. ## Design Through Constraints - Eames defined design as “a plan for arranging elements to accomplish a particular purpose.” - Furse applies this principle to engineering, where code must balance: - Time - Simplicity - Maintainability - Aesthetic quality - The squircle project became a mathematical example of design involving research, false starts, hidden constraints, and refinement. ## Why Squircles Look Different - Apple’s iOS 7 icons replaced conventional rounded squares with more organic-looking squircles. - A rounded square has an abrupt transition between its straight edges and curved corners. - A squircle has continuous curvature around its perimeter, producing a smoother, more unified appearance. - Similar curvature continuity appears in industrial design, such as MacBook corners and earbud cases, where it prevents harsh changes in reflected highlights. ## Modeling the Shape with a Superellipse - To add squircles to Figma, the team needed a precise mathematical description. - Early research suggested that Apple’s shape was a superellipse, a generalized ellipse described by parameters `a`, `b`, and `n`. - With `n = 2`, the formula produces an ellipse; with equal axes, it produces a circle. - Increasing `n` makes the shape increasingly resemble a rounded rectangle, approaching a sharp-cornered rectangle as `n` approaches infinity. - A value around `n = 5` produced an image that looked very similar to an iOS squircle. ## The First False Start - Despite its visual similarity, the superellipse did not match Apple’s actual icon geometry. - Detailed follow-up analysis found a small but consistent discrepancy for every value of `n`. - This meant that simply approximating the superellipse with Bézier curves would not produce the authentic shape. - The investigation therefore moved toward alternative constructions, including sequences of Bézier curves for the corners. The main lesson is that visual resemblance is not enough when reproducing a design precisely: mathematical elegance must be tested against the real artifact, and constraints often reveal the need for a more complex solution.

Read original

iOS Figma Vector Graphics Bezier Curves+2

figmaFeb 7, 20182 min readCurated summary

Web design without a web designer? Xfive turns to Figma. | Figma Blog

Xfive, a web development company without in-house designers, used Figma to redesign its outdated website. Content producer Lubos Kmetko created the redesign and used Figma’s browser-based collaboration, prototyping, commenting, and developer handoff features to involve stakeholders across the company. The experience showed that Figma could make website design accessible to non-designers while reducing communication and implementation friction. ## Website problems and redesign goals - Xfive’s homepage and key sections had fallen behind as the company grew. - The site suffered from: - Outdated Customers and Work sections - Confusing navigation - Too many competing calls to action - Numerous landing pages that were difficult to maintain - Because Xfive typically implements client-provided designs, it did not usually employ dedicated designers. - Lubos Kmetko, a content producer familiar with Figma, took responsibility for the redesign. ## Prototyping and stakeholder collaboration - Lubos redesigned the homepage, Customers section, and Work section. - He streamlined navigation and reduced the number of CTAs and landing pages. - Stakeholders from marketing, sales, production, editorial, development, and operations reviewed the mockups. - Figma’s cloud-based workflow allowed anyone with a browser to: - Open the designs through a shared link - Leave comments - Discuss ideas and interactions - Review changes in real time - Feedback and revisions remained synchronized in one location instead of being scattered across files and messages. ## Improving designer-developer handoff - Approved designs were shared directly through Figma rather than sent as files through email or Box. - Developers could inspect designs in the browser using Code Mode. - Figma provided specifications such as dimensions, colors, and padding, along with export options for CSS, iOS, and Android code. - This reduced version-control problems, guesswork, and dependency on tools such as Avocode or Zeplin. - Developers reported that access to precise design details helped them code faster and more accurately. ## Future use of Figma at Xfive - Xfive viewed the redesign as a starting point for adopting Figma in client projects. - Lubos envisioned replacing emailed PDFs and JPEGs with functional, shareable prototypes. - The company planned to use Figma across the process, from early design discussions and implementation details to developer handoff. Figma enabled Xfive to complete a substantial redesign without a traditional designer and created a more centralized, collaborative workflow. For teams working across disciplines or locations, browser-based prototypes, comments, and inspectable design specifications can significantly simplify both design review and development.

Read original

iOS Figma User Experience Prototyping+4

figmaDec 6, 20172 min readCurated summary

More time, more money: How Figma accelerates agency workflow | Figma Blog

Figma helped Unfold, a 10-person Florida design agency, reduce versioning, collaboration, and handoff problems by keeping work in a shared cloud platform. Its browser-based workflow lets clients, designers, and developers access the same up-to-date files regardless of operating system. Founder Eddie Lobanovskiy estimates the agency saves at least 30% of its communication time and can take on more client work. ## Replacing File Conflicts with Cloud Collaboration - Before Figma, Unfold struggled with overwritten files, conflicting versions, and a patchwork of plugins. - Figma’s cloud-based files provide a single source of truth accessible through a URL. - Teams can share designs, collect feedback, and collaborate without requiring everyone to use the same computer or software. - Unfold used Figma’s Sketch importer to move existing projects into the platform. ## Keeping the Entire Design Process in One Place - Clients can join live brainstorming sessions through Figma’s multiplayer functionality. - Designers and clients can work simultaneously in the same document, accelerating idea generation. - Mood boards are created directly in Figma by dragging images from the web into project files. - High-fidelity designs remain available at the same URL, eliminating repeated exports and uploads. - Pinned comments keep feedback attached to the relevant design frame rather than scattered across email or messaging tools. ## Simplifying Developer Handoff - Previously, Unfold had to accommodate developers using non-Mac computers and sometimes convert files to PSD through Illustrator, which damaged layer structures. - Figma’s code mode lets developers inspect designs, export assets, and retrieve CSS, Android, and iOS specifications. - Developer access remains synchronized with the latest design automatically. - Developers can use view-only access, so clients do not necessarily need paid editor accounts. - Cross-platform access removes the need to persuade clients or developers to purchase specific software or hardware. ## Taking on More Work - Figma made Unfold’s workflow faster and more fluid by reducing administrative and coordination overhead. - The agency found projects more pleasant to manage and felt capable of serving more clients. - The main business benefit was not only saved time, but also fewer process disruptions and smoother collaboration. Figma’s shared, cross-platform workspace gave Unfold a practical way to centralize design, feedback, prototyping, and developer handoff—helping the agency communicate less, move faster, and increase its capacity.

Read original

iOS Figma Prototyping Android+4

figmaJul 24, 20172 min readCurated summary

Figma 2.0: Now with Prototyping and Developer Handoff | Figma Blog

Figma 2.0 expands Figma from a collaborative design tool into a platform for entire product teams. Its two major additions—prototyping and developer handoff—reduce the need to export designs, synchronize files, or rely on separate tools. The release reflects Figma’s broader goal of helping teams build software together around a shared, cloud-based source of truth. ## From Designer Collaboration to Team Collaboration - Figma 1.0 focused on cloud-based design, multiplayer editing, and shared component libraries. - User feedback showed that designers also needed to collaborate with marketers, executives, and engineers. - Figma 2.0 therefore aims to empower entire teams, not just designers working together. ## Integrated Prototyping - Prototyping lets designers present work, gather feedback, secure approval, and test interfaces without leaving Figma. - Figma initially avoided building prototyping features because specialized tools already served that market. - Users wanted to design and present from the same document, maintaining one continuously updated source of truth. - The feature emphasizes slideshows and interactive hotspots rather than advanced motion graphics. - Prototypes update in real time as the underlying design changes, eliminating exporting and syncing. - Designers can: - Add or modify screens while others watch. - Connect frames through nodes in Prototype mode. - Turn objects or components into clickable hotspots. - Reuse hotspot behavior across component instances. - Order frames directly on the canvas for simple presentations. - Control presentations from a phone. - Figma describes prototypes as “living documents” rather than static artifacts, while remaining open to integrations with dedicated prototyping tools. ## Developer Handoff - Designers can share files with developers using view-only access. - Developers receive a Code mode in the properties panel. - Selecting an object reveals spacing measurements and redlines relative to nearby objects. - Developers can access CSS, iOS, and Android specifications. - Information is presented in both: - A scannable table of design attributes. - Generated markup or code. - View-only access means developers do not need paid editor seats, making collaboration more accessible. ## Building a Broader Platform - Figma positions version 2.0 as an all-in-one workflow for design, presentation, and implementation. - The company acknowledges that teams have different tools and processes. - Future plans include deeper integrations and partnerships across the wider design and development ecosystem. Figma 2.0’s practical recommendation is to keep design, prototyping, and developer collaboration in one shared cloud document whenever possible, while continuing to integrate with specialized tools for workflows Figma does not fully cover.

Read original

iOS Figma Prototyping Android+3

figmaMay 8, 20172 min readCurated summary

Figma Mirror for Android | Figma Blog

Figma introduced Mirror for Android on May 9, 2017, bringing real-time mobile previews to Android users and designers. The app reflects selected Figma frames on an Android device and updates instantly as designs change on a computer. Figma also offered the same functionality through a mobile browser, making the feature accessible without installing the app. ## Real-Time Design Mirroring - Users can select a frame in a Figma file on their computer and view it immediately on an Android phone. - Design edits made on the computer are reflected instantly in the mobile preview. - The feature helps designers test how their work appears and behaves on an actual mobile device. - Mirror was already available for iOS before the Android release. ## Browser-Based Alternative - Users who do not want to install the Android app can visit `figma.com/mobile-app` in a mobile browser. - The browser version provides the same basic mirroring functionality. ## Support for Android Design - Android accounted for roughly 52% of the U.S. smartphone market and 82% of the global market at the time. - Figma included preset frame sizes for several popular Android devices, reducing the need to create device layouts from scratch. Figma Mirror for Android made mobile design testing more inclusive and convenient, while the browser option provided a no-download alternative.

Read original

iOS Figma Android Mobile App Development+1

figmaDec 7, 20163 min readCurated summary

Components in Figma | Figma Blog

Figma’s 2016 Components release applies software-engineering ideas such as composition, inheritance, and overrides to interface design. Components let designers reuse shared elements as linked instances, so updates remain consistent while local customizations are preserved. The result is a design workflow that supports both systematic reuse and creative flexibility. ## Designing with Components - Components help designers break complex interfaces into smaller, understandable parts. - Reusable elements can appear in multiple locations, at different sizes and with local modifications. - Unlike duplicated copies, component instances remain connected to their source. - Updates to the original component are automatically reflected across all instances, improving consistency and reducing repetitive work. - Examples include repeated address-book rows containing shared typography, spacing, icons, and graphics. ## Figma’s Design Goals Figma aimed to make Components: - Easy for new users to learn. - Powerful enough for advanced design systems. - Flexible throughout the design process. - Low-overhead, so systematic design improves speed without limiting experimentation. ## Creating and Using Instances - Any frame or selected object can be converted into a component through the toolbar. - Duplicating, copying, pasting, or Alt-dragging a component creates instances rather than independent copies. - Instances can move independently on the canvas while retaining their connection to the source component. - Changes made to the main component propagate immediately to its instances. - Certain internal properties, such as the position and size of nested objects, are restricted to make components easier to maintain. ## Style and Property Overrides - Instance changes are treated as overrides of the original component’s properties. - Designers can override fills, strokes, colors, widths, and properties of nested layers. - Overrides remain intact when the source component changes. - Properties that were not overridden continue to update from the source component. - Overrides can be removed with the “Reset Instance” action. ## Complex and Nested Components - Components can contain instances of other components. - Combining nested components makes it possible to build larger systems from smaller, reusable parts. - Designers can add instances to an existing component or create a new component from selected instances. - Nested components are intended to work like other Figma objects, keeping complex systems manageable. ## Constraints - Components can be combined with Figma’s Constraints feature. - Constraints allow elements to respond to changes in size and position. - Together, components and constraints support reusable designs that adapt more intelligently across layouts. Components provide a practical bridge between design and software development: create shared building blocks once, reuse them widely, and preserve controlled customization through overrides. Teams building consistent, evolving interfaces can use them to reduce duplication while keeping designs adaptable.

Read original

iOS Figma Design Systems React+4