Figma Pages adds an organizational layer within a single design file, letting designers separate brainstorming, wireframes, iterations, and final assets without creating separate documents. The feature supports multiple workflows, including platform-specific designs, shared component libraries, and multiple prototypes. Figma emphasizes that Pages are for organization—not version control—and warns that duplicating large files across Pages may hurt performance.
## Organizing Designs with Pages
- Pages can be added, switched, or deleted from the file’s left-hand panel.
- The Pages menu collapses after use but can be kept open with a control-click.
- Sketch imports preserve the original document’s pages and symbols.
- There is no limit to the number of Pages in a file.
## Common Uses
- Separate brainstorming, wireframing, and polished designs.
- Organize iOS and Android screens on different Pages.
- Store shared components, icons, or other interface elements separately.
- Choose the first Page to control which design appears as the file thumbnail.
- Create separate prototypes within one file.
## Collaboration and Moving Components
- Sharing one Page grants access to the entire file containing it.
- Components can be moved between Pages by right-clicking and choosing **“Move to Page.”**
## Pages Versus Version Control
- Pages should not be used to create copies of designs as a version-control system.
- Figma already provides version history for tracking changes.
- Repeatedly duplicating large designs across Pages can negatively affect performance.
Figma Pages is best used to structure related design work within one accessible file, while Figma’s version history should handle historical snapshots and revisions.
The article highlights ten UI/UX design internships recommended by Figma users, arguing that the best programs offer meaningful design work, mentorship, user research, and opportunities to learn—not merely perks or high compensation. Across companies ranging from Shopify and Facebook to Hotels.ng and Palantir, interns are given varying degrees of responsibility, collaboration, and professional guidance. The strongest internships help students build practical skills and often lead to full-time employment.
## What Makes an Internship Valuable?
- Respondents valued opportunities to practice design, conduct real user testing, and learn from experienced professionals.
- Mentorship was a recurring theme:
- Shopify assigns every intern a staff mentor.
- Spotify provides interns with a designated mentor or manager.
- Perks such as catered meals, generous stipends, travel credits, and office amenities were appreciated but considered secondary to meaningful work and learning.
## Shopify
- Places interns on cross-functional teams to develop communication and collaboration skills.
- Design interns work on deployable products, including Timeline.
- Approximately 80% of interns reportedly return to Shopify or become full-time employees.
- Strong emphasis on individual mentorship.
## Hotels.ng
- Offers a remote, paid UI/UX internship for Nigerian residents through a partnership with the Akwa Ibom State government.
- Interns must complete assigned tasks successfully to remain in the program.
- The program lasts three months.
- Many graduates receive full-time offers from Hotels.ng or other local companies.
## Facebook
- Provides a reported average stipend of about $5,600 per month.
- Interns receive substantial responsibility and are treated similarly to full-time employees.
- The work environment is described as resembling an intensive “college campus.”
## Spotify
- Runs a ten-week program organized into close-knit squads and two-week sprints.
- Interns are treated as “band members,” reinforcing the company’s collaborative culture.
- The product design program is highly design-focused, with strong expectations for visual craft.
- Mentorship and free food are notable parts of the experience.
## Salesforce
- Its Futureforce program gives interns meaningful projects and opportunities to learn design systems.
- Interns participate in social events with executives and receive up to seven days of Volunteer Time Off.
- The program combines professional development with networking and community activities.
## Uber
- Offers health benefits, unlimited vacation, and Uber credits.
- Interns work in an intense but rewarding environment.
- Product design interns may have direct access to senior leaders, whose willingness to listen can give interns significant influence.
## IBM
- Austin’s Maelstrom program guides roughly 15 young designers through four tracks:
- Design research
- Visual design
- UX design
- Front-end development
- Program leaders attribute its success partly to an emphasis on emotional intelligence.
## Airbnb
- Known for a strong design culture, influenced in part by its designer co-founders.
- Offers a close-knit, progressive, and innovative work environment.
- Interns receive travel credits and access to extensive employee perks.
- The company was ranked highly as a workplace in 2016.
## Square
- Gives interns flexibility to explore different types of design problems as their interests develop.
- Recognized for efforts to address gender inequality in technology.
- Interns may work beyond conventional UI design, with opportunities to approach problems creatively and artistically.
## Palantir
- Product design interns focus on solving complex problems rather than making minor visual adjustments.
- The company’s open-source Blueprint style guide reduces repetitive interface work.
- The program emphasizes product thinking and meaningful design challenges.
## Practical Takeaway
When evaluating internships, prioritize mentorship, real product responsibility, cross-functional collaboration, and opportunities to learn from feedback. Compensation and perks are useful, but a program that develops practical design skills and provides a path to future employment is likely to have the greatest long-term value.
Figma announced a Zeplin integration to make it easier for teams to move designs into a developer-focused handoff workflow. The integration supports teams using different design and development processes, allowing Figma frames to be exported directly into Zeplin. However, unlike Figma’s always-current code mode, designs must be re-exported whenever the original Figma file changes.
## Supporting Flexible Design Workflows
- Teams use different tools and processes to design, prototype, and build digital products.
- Figma aims to support these workflows through integrations with complementary tools.
- Zeplin is focused specifically on the developer experience, presenting design specifications and assets in an accessible format for engineers.
## Exporting Figma Designs to Zeplin
The integration can be enabled through the following workflow:
- Download Zeplin and create a project.
- Enable Zeplin in Figma through **Menu → Integrations → Zeplin**.
- Create and select a frame in Figma.
- Choose **Export**, then select **Export to Zeplin**.
- Zeplin opens automatically, where the user can select **Import**.
- The exported Figma design then becomes available for viewing in Zeplin.
## Important Workflow Limitation
- Exported designs are not automatically synchronized with Figma.
- Any updates made to the original Figma design require another export to Zeplin.
- This differs from Figma’s code mode, where developers always see the latest design assets.
Figma presents the integration as part of its broader effort to help design and engineering teams collaborate more efficiently. Teams that rely on Zeplin can now incorporate Figma into their existing handoff process, provided they remember to re-export designs after changes.
Figma argues that interface design courses need tools that minimize technical overhead so professors can focus on design principles. Its browser-based, collaborative platform is presented as accessible across devices, free for educational institutions, and easy for beginners to learn. The post concludes that these features make teaching, feedback, sharing, and group work more efficient.
## The Challenge of Teaching Interface Design
- Interface design remains uncommon in college curricula, often appearing as isolated interdisciplinary courses.
- Professors must teach substantial technical concepts in limited time.
- Traditional design tools can be difficult and time-consuming for students to learn.
## Accessible on Any Computer
- Figma runs in the browser and supports PCs, Macs, Linux systems, and Chromebooks.
- Students can work anywhere with internet access, without downloading large software packages.
- This helps students who do not own high-powered personal computers.
## Free for Educational Institutions
- Figma’s premium version is offered free to educational institutions.
- Schools do not need to negotiate expensive contracts.
- The lack of cost reduces barriers for students from lower-income backgrounds.
## Easy to Learn
- Figma is designed around the core functionality digital designers need.
- Berkeley instructors describe it as lightweight, simple, and intuitive.
- Students with no prior design experience can reportedly learn the basics in under an hour.
- Professors and TAs can concentrate on design principles rather than tool training.
## Technical Support for Classes
- Figma provides in-app chat support for students and instructors.
- The company states that it responds within 24–48 hours on weekdays.
- This reduces the technical-support burden on professors and TAs, especially in large classes.
## Always-Current, Shareable Designs
- Designs are stored online and accessed through a file URL.
- Instructors can view the latest version without requiring students to export or email files.
- Teachers can review work or watch students design in real time.
## Feedback and Version History
- Comments can be pinned directly to specific design frames.
- Students can view feedback immediately and iterate without waiting for in-person meetings.
- Version history shows how a design developed and helps instructors assess contributions in group projects.
## Real-Time Collaboration
- Multiple students can work in the same file simultaneously.
- Cloud collaboration eliminates the need to email files, manage conflicting versions, or take turns editing.
- The post also introduces seamless developer handoff as another benefit, though the provided excerpt does not elaborate on it.
Figma’s combination of low cost, cross-platform access, simple onboarding, collaboration, and built-in feedback makes it a practical classroom tool for teaching design fundamentals rather than software mechanics.
Figma celebrated its first anniversary with “#6DaysofShipping,” releasing a new feature or improvement each day from Monday through Saturday. The initiative aimed to serve both advanced users and beginners, combining powerful workflow enhancements with accessible tips. The post recaps the week’s releases and highlights Figma’s fast, community-driven product development.
## A Week of Daily Releases
- Figma created the release week after users praised the company’s rapid shipping pace.
- The team decided to launch one feature per day for six consecutive days.
- Releases ranged from advanced functionality, such as nested instance swapping, to beginner-friendly resources like a complete keyboard shortcut list.
- The campaign was intended as a fun, unexpected celebration for Figma’s community and first anniversary.
## Scrubbable Inputs
- Users can change property values more quickly by holding **Option**, clicking, and dragging.
- Moving the cursor upward allows values to be “scrubbed” even faster.
- The interaction is designed to speed up design exploration and iterative adjustments.
## Shortcuts for Rounding Corners
- Rectangle corner radii can be adjusted directly by hovering, clicking, and dragging.
- Users can round individual corners by holding **Alt** while clicking and dragging.
- This provides more precise control over shapes without relying solely on numeric inputs.
Figma’s release week demonstrated how small interaction improvements and advanced capabilities can make design work faster and more flexible. The practical recommendation is to explore both the new gestures and the broader shortcut reference to get more out of Figma’s editing workflow.
FigmaTip Roundup 2.0 collects quick workflow lessons shared by Figma users and the Figma team. The tips focus on importing several images efficiently and navigating the canvas faster. Together, they show how simple keyboard shortcuts and layer-panel actions can speed up everyday design work.
## Importing and Placing Multiple Images
- Press **Cmd+Shift+K** to open the image import workflow.
- Select multiple image files at once.
- Click on the canvas to place the images, avoiding the need to import them individually.
## Zooming Directly to an Object
- Double-click the **layer icon** for an object in the Layers panel.
- Figma zooms the canvas to show that object at its full dimensions.
- This provides a quick way to locate and inspect objects without manually navigating or changing zoom levels.
The roundup encourages designers to adopt these small shortcuts and share their own tips with the Figma community.
The post launches Figma’s **#FigmaTip Roundup**, a collection of small, community-shared techniques for discovering less obvious features in Figma. The featured tips focus on faster editing, navigation, and object selection, showing how keyboard shortcuts and property-based commands can streamline design workflows.
## Copying Layer Properties
- Multiple layer properties can be selected and copied to other objects.
- This provides a quicker alternative to manually reproducing styles or settings across layers.
## Canvas Panning Shortcuts
- Press **Z + an arrow key** to pan around the canvas.
- Hold **Shift + Z** to pan using larger movements or “nudges.”
- These shortcuts make navigating large canvases faster without relying on scrollbars or trackpad gestures.
## Selecting Objects with Matching Properties
- The roundup also highlights a feature for selecting objects that share the same properties.
- This can help designers efficiently work with groups of similarly styled or configured objects.
The article encourages designers to explore Figma’s hidden capabilities and share their own discoveries through **#FigmaTip**.
Figma’s Live Embed Kit lets anyone place continuously updated Figma designs and prototypes on websites or inside third-party tools. Embeds use a simple iframe and remain synchronized with the original file, eliminating repeated exports and uploads. Figma presents the kit as a way to improve team communication and signals future platform tools, including a planned API.
## Simple Embedding for Websites and Tools
- Users can select **Share → Public embed** in a Figma file and copy the generated iframe code.
- Developers can integrate Live Embeds into their own products using Figma’s embed documentation.
- Third-party platforms such as Trello, JIRA, and Dropbox Paper can enable Figma embeds for their users.
## Always-Up-to-Date Designs
- Because Figma runs on the web, embedded files stay synchronized with the source document.
- Small changes—such as adjusting padding or replacing an icon—appear automatically in every embed.
- Teams no longer need to re-export designs or upload updated files manually.
## Collaboration Use Cases
- Internal wikis can display live designs alongside project and feature documentation.
- Team messaging apps can let users share the latest design versions in conversations.
- Blogs and project pages can show designs that remain current for readers.
## Broader Platform Direction
- Figma aims to reduce the confusion caused by outdated files scattered across email, Slack, and file-sharing services.
- The Live Embed Kit is described as an early step in expanding Figma’s platform.
- Figma planned to release an API for retrieving additional information from files and incorporating it into new workflows.
The kit is recommended for teams and developers that want design updates to flow automatically into the places where people communicate, document, and build products.
Figma’s Team Library 1.0 turns shared components into a centralized foundation for collaborative design systems. Building on feedback from its February beta, the release improves component discovery, documentation, and organization. Figma argues that its centralized, online platform can keep teams synchronized without third-party tools or custom internal systems.
## A Centralized Source of Truth
- Teams can share buttons, icons, dialogs, and other components across files and with all team members.
- Published components and updates appear immediately in the Team Library.
- Users receive notifications when shared components change and can choose whether to apply updates to their local instances.
- Centralized storage eliminates manual exporting, syncing, and reliance on tools such as Slack, Google Docs, or custom company software.
## Improved Component Browsing
- The beta required repeatedly opening a pop-up that obscured the canvas.
- Team components are now available in a dedicated tab in the left sidebar, alongside layers.
- Designers can drag components directly from the sidebar into their designs.
- A separate local-components tab provides an overview of what will be published.
- The sidebar tabs can be switched quickly with `Alt+1`.
## Built-In Component Documentation
- The beta provided no place to explain how or when components should be used.
- Team Library 1.0 adds documentation fields in the right-hand properties panel.
- Teammates can read this guidance while browsing components, keeping usage information attached to the component itself.
## Better Categorization and Organization
- The beta organized components only by file, which made larger libraries difficult to navigate.
- Components can now also be grouped by frame and group.
- For example, button components placed in a group named “Buttons” appear together under that category.
- Shared component thumbnails can be visually customized by changing the background color of their containing frame.
Figma presents Team Library 1.0 as a practical foundation for building and maintaining living design systems. Teams can adopt shared components with less friction, while documentation and categorization make those systems easier to understand and scale.
Figma introduced Live Embeds for Trello and Jira Software, allowing teams to place Figma designs directly in cards and tickets. Embedded designs update automatically whenever the original Figma file changes, eliminating outdated image exports and reducing the effort designers spend sharing the latest work. The integration is positioned as a way to improve communication between designers, developers, product managers, and other stakeholders.
## Live, Automatically Updated Designs
- Teams can embed Figma files in Trello cards and Jira tickets.
- Changes made in Figma—such as adjusting spacing or colors—appear automatically in the embedded design.
- Everyone can access the current version of a design without searching for files or replacing outdated screenshots.
- The feature reduces reliance on exported PNGs that become obsolete as soon as the design changes.
## Improving Designer–Developer Collaboration
- Trello and Jira are central tools for planning work, tracking deadlines, and coordinating product development.
- Live Embeds help keep design information connected to the tasks where teams already work.
- Atlassian described the integration as a way to streamline communication and make the latest designs easier to find.
## Expanding Figma Integrations
- The Atlassian integration follows a similar Live Embed capability previously introduced for Dropbox Paper.
- Figma emphasizes that its browser-based platform makes it well suited to embedding designs across different workflows.
- The company planned to bring Live Embeds to more tools used by designers and their teams.
## Getting Started
- **Jira Software:** Enable the Figma integration through Atlassian’s marketplace, then paste a Figma URL into a Jira ticket’s design section.
- **Trello:** Enable Figma as a team Power-Up, then attach a Figma URL to a Trello card.
Live Embeds are recommended for teams that want design work to remain synchronized with project-management tasks and accessible to everyone involved in shipping a product.
Figma announced a live integration with Dropbox Paper that lets teams embed Figma designs and prototypes directly into collaborative documents. Embedded content updates automatically, reducing confusion over outdated files and keeping project stakeholders aligned. The integration reflects Figma’s broader goal of making design collaboration accessible across disciplines and tools.
## Live Figma Embeds in Dropbox Paper
- Figma designs and prototypes can now appear as live embeds inside Dropbox Paper documents.
- Updates made to the original Figma file are reflected immediately in the Paper document.
- The feature helps project managers, engineers, and designers work from the same, current version of a design.
- It eliminates the need to search for or repeatedly share updated design files.
## Broader Collaboration Across Teams
- Dropbox Paper is positioned as a collaborative workspace for teams with Dropbox accounts.
- Paper already supported integrations with services such as YouTube, GitHub, and Facebook.
- Figma’s addition extends design collaboration beyond the design application itself.
- The integration keeps teams in context while discussing and acting on design work.
## Simple, Lightweight Setup
- Users can create an embed by copying and pasting a Figma project URL into Dropbox Paper.
- The live document appears immediately without a complicated configuration process.
- Figma removed unrelated application components from the embed, making it lightweight and fast.
The integration is recommended for teams that use Dropbox Paper to coordinate work around designs. By embedding live Figma content rather than static exports, teams can maintain a more reliable and up-to-date source of truth.
Figma introduced emoji support in 2017 after users repeatedly requested it, emphasizing that emojis had become essential to modern digital communication and interface design. The main technical challenge was ensuring consistent rendering across operating systems without sacrificing visual quality. Figma chose individually cached, 64×64 full-color PNGs, providing sharper and more memory-efficient results than Slack’s single large sprite image.
## Why Emoji Support Mattered
- Designers need to preview interfaces with the same visual content users will see in real products.
- Emojis communicate tone, emotion, and nuance in advertising, messaging, email, and social media designs.
- Some teams reportedly left Figma because the feature was missing.
- Native browser rendering was unsuitable because emoji appearance varies between operating systems and platforms.
## The History of Emoji and Unicode
- Emojis originated in Japan in 1999, when Shigetaka Kurita created 176 pictorial characters to supplement text.
- Competing mobile carriers developed incompatible emoji sets, causing inconsistent rendering.
- In 2009, the Unicode Consortium standardized emoji identifiers alongside other written characters.
- Unicode defines the character code and general design guidelines, but companies remain free to create their own artwork.
- As a result, the same emoji can look substantially different on Apple, Google, Facebook, Twitter, Samsung, and other platforms.
## Why Cross-Platform Rendering Was Difficult
- Figma is a collaborative, cross-platform application, so Mac and Windows users need to see identical designs.
- Depending on each operating system’s emoji library could make the same file appear differently to different users.
- Visual inconsistencies can alter an emoji’s perceived meaning, creating communication problems.
## Figma’s Rendering Approach
- Slack’s approach used a large PNG containing Apple’s emoji set and displayed relevant regions as needed.
- That method was fast but limited by lower color quality and poor scalability at larger sizes.
- Figma rejected the sprite-image approach because designers are especially sensitive to low-resolution visuals.
- Instead, Figma used separate 64×64 full-color PNG files for each emoji.
- Individual emoji files load slightly slower the first time they are used, but are cached for faster subsequent use.
- This approach provides higher resolution and uses memory more efficiently than one massive image.
Figma’s solution prioritized consistent, high-quality rendering over the fastest possible initial load. For design tools and other visually demanding collaborative applications, individually cached assets can be a better tradeoff than relying on platform-native rendering or low-resolution sprite sheets.
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.
Figma introduced Image Adjustments in 2017, bringing basic photo-filtering capabilities directly into its browser-based design tool. The feature lets designers modify exposure, contrast, saturation, temperature, tint, highlights, and shadows without exporting images to Photoshop or using workarounds. Figma positioned it as a convenience for quick edits—not a replacement for professional image-editing software.
## Figma’s Return to Photo Editing
- Figma began partly as a Photoshop competitor, with early experiments involving browser-based photo filters and masks.
- The new feature revisited that original direction in a focused, practical way.
## Image Adjustment Features
- Designers can adjust:
- Exposure
- Contrast
- Saturation
- Temperature
- Tint
- Highlights
- Shadows
- Adjustments are available after placing an image on the canvas.
- Users access the filtering controls through the **Fill** section of Figma’s right-hand properties panel.
## Designed for Quick Fixes
- The feature eliminates the need to export images to Photoshop for simple changes.
- Figma carefully balanced adjustment ranges to avoid undesirable results, such as overly blown-out images at high exposure levels.
- The tools are intended to simplify common design tasks rather than provide comprehensive photo-editing capabilities.
Figma’s Image Adjustments are best understood as a convenient set of in-product controls for fast visual corrections. Professional photographers and advanced editors will still need dedicated software, but designers can now handle routine image tweaks directly in Figma.
Figma introduced Guides in response to frequent user requests for faster alignment and positioning tools. The feature adds draggable horizontal and vertical ruler guides that complement Layout Grids, with options for frame-level organization, pixel nudging, and undo support.
## Creating and Using Guides
- Enable rulers through **Main menu → View → Show rulers**.
- Hover over the top or side ruler to see the offset, then click to create a Guide.
- Guides appear as thin red lines and can be dragged to new positions.
- Multiple Guides can be added by clicking several ruler offsets.
## Managing Guides
- Delete a Guide by selecting it and pressing **Delete**, or drag it off the canvas.
- Guides disappear when ruler view is disabled.
- Accidental changes can be undone with **Command-Z**.
- Arrow keys allow pixel-by-pixel nudging.
## Frame-Level Guides
- Dragging a Guide into a frame converts it into a frame-level Guide.
- This keeps the overall canvas cleaner when using many Guides.
- Frame-level Guides work only on top-level frames; moving such a frame into another frame causes the Guides to disappear.
The feature provides a lightweight, flexible alternative to Layout Grids for aligning designs. Users can enable rulers and create Guides as needed, while frame-level support helps organize complex canvases.