# mobile optimization

Mobile optimization is the practice of adapting websites and apps for mobile devices, including responsive layouts, touch interaction, and performance on mobile networks.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to embed a Booking.com widget in Webflow without breaking mobile

DevFeed: [How to embed a Booking.com widget in Webflow without breaking mobile](<https://devfeed.tech/articles/how-to-embed-a-booking-com-widget-in-webflow-without-breaking-mobile-147025.md>)

Original publisher: [Read original article](<https://www.webflow.com/blog/embed-booking-com-widget-webflow>)

Author: Ismail Ajagbe

Published: 2026-11-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [Webflow Blog](<https://devfeed.tech/sources/webflow-blog.md>)

Topics: [webflow](<https://devfeed.tech/topics/webflow.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [booking](<https://devfeed.tech/tags/booking.md>), [box](<https://devfeed.tech/tags/box.md>), [code](<https://devfeed.tech/tags/code.md>), [element](<https://devfeed.tech/tags/element.md>), [guides](<https://devfeed.tech/tags/guides.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [webflow](<https://devfeed.tech/tags/webflow.md>), [widget](<https://devfeed.tech/tags/widget.md>)

### AI overview

Booking.com Affiliate Partner search and map widgets can be embedded in Webflow, but they send visitors to Booking.com to complete bookings. To prevent mobile overflow, set `data-width` to `100%` and `data-height` to a pixel number or `auto`; `100%` height causes a script error and blank widget. Paste the complete generated `<ins>` and `<script>` code into a Code Embed element, then preview or publish to check rendering and affiliate attribution. The embed requires an active affiliate account and a paid Webflow Site plan or qualifying Workspace; CMS destination pages require a CMS plan. Separate breakpoint-specific embeds are possible, but hidden widgets still load and each makes a request. Third-party script consent controls may block loading, and the canvas itself shows only a placeholder.

### Source excerpt

Add a Booking.com affiliate search box to a Webflow page with a Code Embed element, size it for mobile and fix widgets that don't render.

## Opening groundcover on Duo and looking at our own mobile RUM

DevFeed: [Opening groundcover on Duo and looking at our own mobile RUM](<https://devfeed.tech/articles/opening-groundcover-on-duo-and-looking-at-our-own-mobile-rum-141939.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/opening-groundcover-on-duo-and-looking-at-our-own-mobile-rum>)

Author: Anais Dotis

Published: 2026-11-18T10:05:00Z

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [real user monitoring](<https://devfeed.tech/topics/real-user-monitoring.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [dogfooding](<https://devfeed.tech/topics/dogfooding.md>), [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Android](<https://devfeed.tech/topics/android.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [android](<https://devfeed.tech/tags/android.md>), [apple-store](<https://devfeed.tech/tags/apple-store.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [customer](<https://devfeed.tech/tags/customer.md>), [duo](<https://devfeed.tech/tags/duo.md>), [evals](<https://devfeed.tech/tags/evals.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [hermes](<https://devfeed.tech/tags/hermes.md>), [infrastructure-monitoring](<https://devfeed.tech/tags/infrastructure-monitoring.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [rum](<https://devfeed.tech/tags/rum.md>)

### AI overview

groundcover's mobile RUM links real user sessions to backend traces: the React Native SDK captures screens, taps, logs and network calls, while Exceptions records crashes, ANRs and hangs and Vitals tracks slow or frozen frames and app starts per screen. The article says the Flutter package is a release candidate with the same signals and UI. The team also describes using its React Native SDK in its own apps, where it found and fixed missing Hermes stack frames and dropped native crash traces. Separately, testing groundcover on an iPhone Duo revealed a small-screen usability issue: the team pinned key sidebar controls and collapsed "over time" charts on screens 650px tall or shorter, remembering when users reopen them.

### Source excerpt

A customer's experience with groundcover mobile RUM on Duo

## I Followed the Textbook Fix for PageSpeed and My Site Got Slower

DevFeed: [I Followed the Textbook Fix for PageSpeed and My Site Got Slower](<https://devfeed.tech/articles/i-followed-the-textbook-fix-for-pagespeed-and-my-site-got-slower-125755.md>)

Original publisher: [Read original article](<https://hackernoon.com/i-followed-the-textbook-fix-for-pagespeed-and-my-site-got-slower?source=rss>)

Author: NXTO

Published: 2026-11-10T10:12:31Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Compression](<https://devfeed.tech/topics/compression.md>), [Font](<https://devfeed.tech/topics/font.md>), [CSS](<https://devfeed.tech/topics/css.md>), [web animation](<https://devfeed.tech/topics/web-animation.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [animations](<https://devfeed.tech/tags/animations.md>), [compression](<https://devfeed.tech/tags/compression.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [css](<https://devfeed.tech/tags/css.md>), [css-animation-performance](<https://devfeed.tech/tags/css-animation-performance.md>), [css-animations](<https://devfeed.tech/tags/css-animations.md>), [font](<https://devfeed.tech/tags/font.md>), [largest-contentful-paint](<https://devfeed.tech/tags/largest-contentful-paint.md>), [loading](<https://devfeed.tech/tags/loading.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [pagespeed](<https://devfeed.tech/tags/pagespeed.md>), [self-hosted-web-fonts](<https://devfeed.tech/tags/self-hosted-web-fonts.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [web-performance](<https://devfeed.tech/tags/web-performance.md>), [website](<https://devfeed.tech/tags/website.md>), [website-optimization](<https://devfeed.tech/tags/website-optimization.md>)

### AI overview

A blanket fix for render-blocking fonts made this site's mobile PageSpeed score fall from 86 to 77: fonts loaded after first paint, causing layout shift without improving First Contentful Paint. The author then used the report and `curl` to find that production compression was off, a component's hidden `@import` delayed the main stylesheet, and an invisible, staggered hero animation held back largest contentful paint. After enabling Express compression, replacing the imported font with a system stack, shortening the animation, and self-hosting fonts with only above-the-fold Latin subsets preloaded, the score reached 99. The author's takeaway is to verify diagnostics and measure changes individually; asynchronous font loading may help some sites but harmed this one.

### Source excerpt

See how fixing font loading, missing compression, and CSS animations helped improve a website's mobile PageSpeed score from 86 to 99.

## Testing Foldable Devices: Process, Tools, and Best Practices

DevFeed: [Testing Foldable Devices: Process, Tools, and Best Practices](<https://devfeed.tech/articles/testing-foldable-devices-process-tools-and-best-practices-121138.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/testing-foldable-devices/>)

Author: Sanjaykumar Ghinaiya

Published: 2026-11-06T12:23:49Z

Content type: tutorial

Language: en

Sources: [TestGrid](<https://devfeed.tech/sources/testgrid-blog.md>)

Topics: [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [foldable-devices](<https://devfeed.tech/tags/foldable-devices.md>), [mobile-app-testing](<https://devfeed.tech/tags/mobile-app-testing.md>), [process](<https://devfeed.tech/tags/process.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-foldable-devices](<https://devfeed.tech/tags/testing-foldable-devices.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Foldable testing checks whether apps preserve behavior and usability as screens change size, posture, orientation, or window mode. Cover fold and unfold transitions, layout and hinge areas, state restoration, multitasking, and orientation; include functional, UI, usability, compatibility, and performance checks. Start by defining supported device configurations and posture-specific user scenarios, then prepare data and environments, combine manual exploration with automation, and record device state and reproduction steps when analyzing failures. Android Emulator supports early configuration testing; physical devices are needed to assess hinge behavior, touch, sensors, GPU rendering, and manufacturer-specific software, so the two complement each other. Android Studio and Jetpack WindowManager expose foldable configurations and layout or hinge information; Appium supports Android and iOS automation, while Espresso targets native Android UI behavior.

### Source excerpt

Foldable smartphones and devices aren't a niche segment anymore. The market is growing steadily and is expected to reach $115.86 billion by 2034 from $41.43 billion in 2026, according to recent industry research. However, this trend leads us to an important question: Do apps designed for conventional smartphones work accurately on foldable devices? We'll uncover [...]

## Adapting a SwiftUI Courier App for iPhone Duo's Foldable Display

DevFeed: [Adapting a SwiftUI Courier App for iPhone Duo's Foldable Display](<https://devfeed.tech/articles/adapting-a-swiftui-courier-app-for-iphone-duo-s-foldable-display-106879.md>)

Original publisher: [Read original article](<https://hackernoon.com/adapting-a-swiftui-courier-app-for-iphone-duos-foldable-display?source=rss>)

Author: Philip Ellis

Published: 2026-10-29T20:29:54Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [SwiftUI](<https://devfeed.tech/topics/swiftui.md>), [iphone](<https://devfeed.tech/topics/iphone.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [appstores](<https://devfeed.tech/topics/appstores.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [actions](<https://devfeed.tech/tags/actions.md>), [added](<https://devfeed.tech/tags/added.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [appearance](<https://devfeed.tech/tags/appearance.md>), [display](<https://devfeed.tech/tags/display.md>), [duo](<https://devfeed.tech/tags/duo.md>), [foldable-phones-ui](<https://devfeed.tech/tags/foldable-phones-ui.md>), [ios-app-development](<https://devfeed.tech/tags/ios-app-development.md>), [ios-simulator](<https://devfeed.tech/tags/ios-simulator.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [iphone-duo](<https://devfeed.tech/tags/iphone-duo.md>), [iphone-duo-app-design](<https://devfeed.tech/tags/iphone-duo-app-design.md>), [iphone-duo-ui-testing](<https://devfeed.tech/tags/iphone-duo-ui-testing.md>), [map](<https://devfeed.tech/tags/map.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [screenshot](<https://devfeed.tech/tags/screenshot.md>), [store](<https://devfeed.tech/tags/store.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>), [swiftui-sheets](<https://devfeed.tech/tags/swiftui-sheets.md>), [xcode-27-1](<https://devfeed.tech/tags/xcode-27-1.md>)

### AI overview

The excerpt describes adapting a SwiftUI courier app for the iPhone Duo using iOS 27.1 simulator and Xcode 27.1 beta tooling. The app measures the sheet and map frames with `onGeometryChange` to detect docking, then shares that placement state across views. When docked, it hides the navigation bar and overlays reachable controls on the map; Dynamic Type and `ViewThatFits` allow controls to wrap, and the bottom sheet's medium detent is removed or restored according to placement while preserving useful selection state. The map gets trailing safe-area padding for the docked sheet, and its route is refit after layout changes; the 300 ms delay is an app-specific workaround. For screenshots, the team selected the largest nonblank display image, checked capture dimensions, restored unfolded posture after simulator reboot, and launched fixture scenes directly. These capture workarounds do not replace testing real navigation. The excerpt notes its observations are specific to the beta tooling and that the app was not tested on the announced touchscreen MacBook Pro.

### Source excerpt

How we adapted our courier app for iPhone Duo: reachable navigation, usable side sheets, map framing after resizing, and App Store screenshot preparation.

## Web Performance Optimization: Practical Techniques for Building Faster Websites

DevFeed: [Web Performance Optimization: Practical Techniques for Building Faster Websites](<https://devfeed.tech/articles/web-performance-optimization-practical-techniques-for-building-faster-websites-90897.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/web-performance-optimization-practical-techniques-for-building-faster-websites/>)

Author: Businessnewsbreak USA

Published: 2026-10-19T19:32:17Z

Content type: article

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [animations](<https://devfeed.tech/tags/animations.md>), [application](<https://devfeed.tech/tags/application.md>), [array](<https://devfeed.tech/tags/array.md>), [assets](<https://devfeed.tech/tags/assets.md>), [async](<https://devfeed.tech/tags/async.md>), [automated](<https://devfeed.tech/tags/automated.md>), [await](<https://devfeed.tech/tags/await.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [building](<https://devfeed.tech/tags/building.md>), [faster](<https://devfeed.tech/tags/faster.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-optimization](<https://devfeed.tech/tags/performance-optimization.md>), [practical](<https://devfeed.tech/tags/practical.md>), [techniques](<https://devfeed.tech/tags/techniques.md>), [web](<https://devfeed.tech/tags/web.md>), [web-performance](<https://devfeed.tech/tags/web-performance.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

The article recommends measuring before optimizing, using Core Web Vitals (LCP, INP, CLS) alongside browser tools and real-user data to find bottlenecks. Practical steps include compressing and sizing responsive images, reserving space to reduce layout shifts, and lazy-loading below-the-fold images while avoiding delays to prominent content. It distinguishes deferred module scripts from non-module scripts using `defer`, and suggests loading optional JavaScript on demand while cautioning that excessive code splitting adds requests. Other techniques include batching layout reads and writes, setting cache policies suited to versioned assets versus frequently changing HTML, enabling Brotli or gzip, and yielding between long tasks or using Web Workers for suitable computation. The article stresses profiling and comparable measurements: gains depend on the page and workload, and a Lighthouse score alone does not represent every user experience.

### Source excerpt

null Continue reading Web Performance Optimization: Practical Techniques for Building Faster Websites on SitePoint.

## Beyond Lazy Loading: How to Build Faster Websites with Responsive Images

DevFeed: [Beyond Lazy Loading: How to Build Faster Websites with Responsive Images](<https://devfeed.tech/articles/beyond-lazy-loading-how-to-build-faster-websites-with-responsive-images-85306.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/beyond-lazy-loading-how-to-build-faster-websites-with-responsive-images/>)

Author: Businessnewsbreak USA

Published: 2026-10-11T17:44:26Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Page Speed Optimization](<https://devfeed.tech/topics/page-speed-optimization.md>), [lazy loading](<https://devfeed.tech/topics/lazy-loading.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Responsive Design](<https://devfeed.tech/topics/responsive-design.md>), [Image processing](<https://devfeed.tech/topics/image-processing.md>), [alt text](<https://devfeed.tech/topics/alt-text.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [article](<https://devfeed.tech/tags/article.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [lazy-loading](<https://devfeed.tech/tags/lazy-loading.md>), [web](<https://devfeed.tech/tags/web.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

This tutorial explains how to optimize website images with responsive image markup, generated image variants, alternative formats, art direction, and selective lazy loading. It also covers loading priorities, intrinsic dimensions, accessibility, and performance measurement across devices.

### Source excerpt

null Continue reading Beyond Lazy Loading: How to Build Faster Websites with Responsive Images on SitePoint.

## Daily Must Reads and Better Reading Layouts

DevFeed: [Daily Must Reads and Better Reading Layouts](<https://devfeed.tech/articles/daily-must-reads-and-better-reading-layouts-89234.md>)

Original publisher: [Read original article](<https://changelog.devfeed.tech/daily-must-reads-and-better-reading-layouts>)

Published: 2026-10-06T00:00:00Z

Content type: release

Language: en

Sources: [devfeed.tech Changelog](<https://devfeed.tech/sources/devfeed-tech-changelog.md>)

Topics: [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Edge](<https://devfeed.tech/topics/edge.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>), [Text-based user interface](<https://devfeed.tech/topics/tui.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [article](<https://devfeed.tech/tags/article.md>), [bottom-navigation](<https://devfeed.tech/tags/bottom-navigation.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [edge](<https://devfeed.tech/tags/edge.md>), [focus](<https://devfeed.tech/tags/focus.md>), [github](<https://devfeed.tech/tags/github.md>), [grid](<https://devfeed.tech/tags/grid.md>), [list](<https://devfeed.tech/tags/list.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

This release introduces Daily Must Reads for signed-in readers on the web app and in Chrome and Edge, with reading progress, bookmarks, and supported MCP agent integration. It also adds persistent grid and compact list layouts, improves mobile navigation and loading behavior, and updates pagination, accessibility, and admin controls.

### Source excerpt

This release adds a new daily reading flow, makes it easier to control how feeds are displayed, and smooths out several rough edges across web, extensions, and admin. Now Available Daily Must Reads are now available for signed-in readers on the web app and in Chrome and Edge. You can open today's picks from the navbar, see why each article was selected, track reading progress, and bookmark items quickly. Must Reads also integrate with supported MCP agents, and admins can inspect a reader's saved daily selection and reading status in admin. Reading streaks now include weekly progress and milestone celebrations, and you can open today's Must Reads directly from the streak panel when available. Polished Reading Experience You can now switch between grid and compact list views right beside Filters across feeds, Read later, Trending, and topic and source feeds. Your choice is remembered, so you can keep the layout that fits how you like to scan. Mobile navigation is easier to use with a stacked header, clearer bottom navigation, and better access to secondary destinations through the account menu. Article cards stay readable on narrow screens with wrapping titles and touch-sized bookmark controls. Compact list mode is easier to scan with single-line titles, aligned columns, and compact bookmark controls. Filter dropdowns keep labels readable without clipped text or horizontal scrollbars. Loading placeholders stay aligned with the selected layout, avoiding flashes between grid and list states. Startup work on high-traffic pages is reduced by deferring hidden account tools and invitation artwork until needed, prioritizing the first visible cover image, and using smaller GitHub avatars. Directly opened articles also show sooner, even if the background feed is still loading or fails. Fixes and Reliability My feed pagination in Chrome and Edge new tabs no longer stops after the first 24 articles when the page is visible but the address bar keeps focus. Pagination continues in

## The Death of the Static UI: Building Context-Aware Mobile Apps in 2026

DevFeed: [The Death of the Static UI: Building Context-Aware Mobile Apps in 2026](<https://devfeed.tech/articles/the-death-of-the-static-ui-building-context-aware-mobile-apps-in-2026-23054.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/the-death-of-the-static-ui-building-context-aware-mobile-apps-in-2026-ddd06d25a473?source=rss----86fb29d7cc6a---4>)

Author: Rudraksh Shukla

Published: 2026-09-14T17:02:27Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Dynamic AI user experience](<https://devfeed.tech/topics/dynamic-ai-user-experience.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [layout](<https://devfeed.tech/topics/layout.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [material-you](<https://devfeed.tech/topics/material-you.md>), [Dark Mode](<https://devfeed.tech/topics/dark-mode.md>), [Android](<https://devfeed.tech/topics/android.md>), [ML Kit](<https://devfeed.tech/topics/ml-kit.md>), [Spotify](<https://devfeed.tech/topics/spotify.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerometer](<https://devfeed.tech/tags/accelerometer.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [balance](<https://devfeed.tech/tags/balance.md>), [boost](<https://devfeed.tech/tags/boost.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [can](<https://devfeed.tech/tags/can.md>), [context](<https://devfeed.tech/tags/context.md>), [death](<https://devfeed.tech/tags/death.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-apps](<https://devfeed.tech/tags/mobile-apps.md>), [mobile-development](<https://devfeed.tech/tags/mobile-development.md>), [static](<https://devfeed.tech/tags/static.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

The article's central recommendation is to make mobile interfaces adapt to context using local signals and on-device inference. It describes a Flutter pipeline that collects motion, light, battery, time and usage data, predicts intent, then updates the widget tree through reactive streams; examples include larger, simpler controls while moving and richer layouts when browsing. It names tflite_flutter, Google ML Kit, Core ML bridges and sensor packages, and suggests small quantized models, low-rate sampling, battery-aware work and background isolates for heavier inference. It also highlights tradeoffs: adaptive screens complicate QA, so context should be injectable for tests; designers should define bounds, adaptation should occur at stable moments, and users should be able to inspect and reset personalization. The article presents local inference as a privacy measure and mentions federated learning and differential privacy for model improvement, while noting that cited business figures are directional marketing research.

### Source excerpt

Every app you've ever shipped made the same quiet assumption: the interface is a fixed thing. You design a screen, you lay out the widgets, and every user sees the same arrangement in the same order -- a 22-year-old on a commuter train at 8am and a 60-year-old at home on a Sunday get pixel-identical layouts. For thirty years that was simply what a UI was. That assumption is dying. In 2026 the leading mobile apps treat the interface as a live surface that reshapes itself in real time -- reordering navigation, resizing touch targets, shifting color and density, surfacing the one action you're most likely to want next -- driven by on-device signals about who you are, where you are, and what you're doing right now. The static screen is becoming the exception, not the default. Here's what's actually driving it, what it takes to build, and what it looks like in code -- with Flutter examples throughout. From static layout to living surface The old personalization playbook was recommendation, not adaptation. Netflix reordered a content row; Spotify built you a playlist. The chrome around those recommendations -- the navigation, the layout, the visual system -- stayed frozen. Context-aware UX pushes personalization down into the interface itself. Concretely, an adaptive UI reacts to signals like these: Motion and activity -- accelerometer and gyroscope tell you the user is walking, driving, or still. A UI can enlarge touch targets and simplify layout when it detects movement, cutting mis-taps. Location and environment -- outdoors in bright light, boost contrast and switch to a high-legibility mode; on a known Wi-Fi network at home, load richer media. Time and calendar -- automatic dark mode at night, a leaving-for-a-meeting layout when the next calendar event is 15 minutes out. Usage history -- promote the three features this user actually touches, demote the ones they never open. A finance app foregrounds transfer for a power user and check balance for a casual one. Device and networ

## Preparing your app for broader memory limits

DevFeed: [Preparing your app for broader memory limits](<https://devfeed.tech/articles/preparing-your-app-for-broader-memory-limits-88703.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/preparing-your-app-for-broader-memory-limits>)

Author: Blair Harmon

Published: 2026-08-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [memory price increases](<https://devfeed.tech/topics/memory-price-increases.md>), [Macrobenchmark](<https://devfeed.tech/topics/macrobenchmark.md>), [memory pool](<https://devfeed.tech/topics/memory-pool.md>), [adb](<https://devfeed.tech/topics/adb.md>), [Crashlytics](<https://devfeed.tech/topics/crashlytics.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [human-in-the-loop UX](<https://devfeed.tech/topics/human-in-the-loop-ux.md>)

Tags: [adb](<https://devfeed.tech/tags/adb.md>), [android](<https://devfeed.tech/tags/android.md>), [android-15](<https://devfeed.tech/tags/android-15.md>), [android-vitals](<https://devfeed.tech/tags/android-vitals.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [crashlytics](<https://devfeed.tech/tags/crashlytics.md>), [limits](<https://devfeed.tech/tags/limits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [product-news](<https://devfeed.tech/tags/product-news.md>)

### AI overview

Android is expanding per-app memory limits across device RAM configurations, and apps that exceed them may be slowed or terminated. The article explains how zRAM swapping and process termination work, then outlines ways to measure and optimize memory use with Android vitals, Crashlytics, ProfilingManager, and adb commands.

### Source excerpt

A great user experience is central to Android's mission, and delivering on that promise requires keeping devices fast, responsive, and reliable.

## The Most Expensive Milliseconds Are Unmeasured

DevFeed: [The Most Expensive Milliseconds Are Unmeasured](<https://devfeed.tech/articles/the-most-expensive-milliseconds-are-unmeasured-19739.md>)

Original publisher: [Read original article](<https://medium.com/expedia-group-tech/the-most-expensive-milliseconds-are-unmeasured-d6cfaaca881d?source=rss----38998a53046f---4>)

Author: Divya Gupta Arora

Published: 2026-06-03T17:11:58Z

Content type: article

Language: en

Sources: [Expedia](<https://devfeed.tech/sources/expedia.md>)

Topics: [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [apps](<https://devfeed.tech/tags/apps.md>), [backend](<https://devfeed.tech/tags/backend.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [button](<https://devfeed.tech/tags/button.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [compare](<https://devfeed.tech/tags/compare.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [component](<https://devfeed.tech/tags/component.md>), [crash](<https://devfeed.tech/tags/crash.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [devops](<https://devfeed.tech/tags/devops.md>), [domain](<https://devfeed.tech/tags/domain.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experience](<https://devfeed.tech/tags/experience.md>), [feature](<https://devfeed.tech/tags/feature.md>), [health](<https://devfeed.tech/tags/health.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [latency](<https://devfeed.tech/tags/latency.md>), [login](<https://devfeed.tech/tags/login.md>), [metric](<https://devfeed.tech/tags/metric.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [time-to-interactive](<https://devfeed.tech/tags/time-to-interactive.md>)

### AI overview

Expedia Group extended Native Time to Interactive (NTTI) across login screens to measure when visible, essential components are ready for interaction, rather than when a screen merely renders. NTTI is the time from screen start until the last key component is interactive. The team defined usable states and key components per screen, standardized comparable measurement for iOS and Android, and validated consistency across releases. The metric exposed platform differences--such as iOS main-thread and lifecycle constraints and Android device and OEM variation--and helped teams connect changes to traveler experience and catch regressions earlier. It informs technical investment and release-readiness discussions, but is not yet a formal rollout blocker; the team intends to treat degradation as a prompt to investigate. NTTI is an early guardrail, not a measure of user intent or behavior, proof of causality, or a standalone release signal.

### Source excerpt

Expedia Group Technology -- EngineeringHow a screen-level performance metric reshaped platform decisions, engineering ownership, and release disciplinePhoto by Pietro De Grandi on Unsplash For the last few years, my responsibility has been straightforward to state but hard to execute -- owning the traveler login experience across mobile platforms. Not just whether a feature works, but whether it feels responsive, predictable, and trustworthy in the moments that matter most. During login, those moments are unforgiving: if a login screen hesitates travelers don't interpret it as 'a slow render', they interpret it as risk. And when the majority of travelers interact through our mobile apps, performance stops being a technical concern and becomes a product promise. This post is a case study of how, within Expedia Group™'s login domain, we extended Native Time to Interactive (NTTI) across login screens -- moving performance from a late-stage check to a first-class signal we can use to validate technology investments, compare platform behavior, and prevent silent regressions as we ship. The Problem: Mobile reliability rarely fails loudly Mobile performance rarely breaks with a crash. It usually degrades quietly, a button takes a beat longer to respond a screen looks ready, but taps don't register the UI stutters just enough to feel "off" Those are the expensive milliseconds -- because they erode trust without triggering obvious alarms. In our login flows, we were shipping consistently, evolving a major part of our stack, and supporting increasing product complexity. Yet we didn't have a consistent way to answer the user's real question -- "When can I actually use this screen?" Why our existing signals failed We were not blind. We tracked many useful things, crashes and ANRs backend latency and service SLIs some component-level timing signals limited Time to Interactive tracking on onboarding and initial login But we had a gap -- we had visibility into system health, not screen

## How we improved image download sizes on Medium with just four characters

DevFeed: [How we improved image download sizes on Medium with just four characters](<https://devfeed.tech/articles/how-we-improved-image-download-sizes-on-medium-with-just-four-characters-20321.md>)

Original publisher: [Read original article](<https://medium.engineering/how-we-improved-image-download-sizes-on-medium-with-just-four-characters-9621b0ebb291?source=rss----2817475205d3---4>)

Author: Scott Batson

Published: 2026-05-18T15:29:29Z

Content type: article

Language: en

Sources: [Medium](<https://devfeed.tech/sources/medium.md>)

Topics: [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Image](<https://devfeed.tech/topics/image.md>), [Page Speed Optimization](<https://devfeed.tech/topics/page-speed-optimization.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [AVIF Images](<https://devfeed.tech/topics/avif-images.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [about](<https://devfeed.tech/tags/about.md>), [adapting](<https://devfeed.tech/tags/adapting.md>), [all](<https://devfeed.tech/tags/all.md>), [angular](<https://devfeed.tech/tags/angular.md>), [archive](<https://devfeed.tech/tags/archive.md>), [asset](<https://devfeed.tech/tags/asset.md>), [away](<https://devfeed.tech/tags/away.md>), [base](<https://devfeed.tech/tags/base.md>), [based](<https://devfeed.tech/tags/based.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [code](<https://devfeed.tech/tags/code.md>), [context](<https://devfeed.tech/tags/context.md>), [download](<https://devfeed.tech/tags/download.md>), [html](<https://devfeed.tech/tags/html.md>), [image](<https://devfeed.tech/tags/image.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [just](<https://devfeed.tech/tags/just.md>), [medium](<https://devfeed.tech/tags/medium.md>), [programming](<https://devfeed.tech/tags/programming.md>), [technology](<https://devfeed.tech/tags/technology.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article says adding `auto, ` to the `sizes` attribute of lazy-loaded images lets supporting browsers choose an image variant using layout and other context, reducing downloaded image data; the author reports a 7% reduction in image downloads for Medium's home feed on a small, non-mobile display. Earlier `srcset` lets browsers select among dimensions of the same image, while `<picture>` lets developers prescribe different images for conditions such as dark mode or screen layout. Because images often load before layout is known, `sizes` can guide selection but may require complex breakpoint rules. The proposed `auto` value uses layout information available for lazy-loaded images. The article says unsupported browsers ignore the unparseable rule, and notes WebKit support added March 24, 2026; it does not provide broader measured results.

### Source excerpt

HTML images just got better, with the subtlest change to your codebasePhoto by Adi Suyatno I know what you're thinking. Scott, I landed on Medium on a small but not mobile-small display and the download chunk related to images in my home feed was like 7% smaller. First of all, thank you for noticing. Second, what if I told you that you too can improve your total asset download size by adding just four characters to your code base? Sounds too good to be true, right? Well, I'm here to tell you, it's true... after I explain how we got here. The history of images on the web As a web developer, you've probably spent a lot of time thinking about and fighting with images. According to the HTTP Archive, even in today's modern landscape of "JavaScript everywhere" the majority of most website's transfer size is images. We've moved away from the "hero image on every page" ethos, but still we're an image-heavy internet. When I was getting my start in web development in 2010ish, we were still adapting to a "mobile-friendly" world. The majority of the web was built on WordPress. We didn't have a way back then to dynamically load an optimized image. 3G connections were the primary speed in the US for viewing the internet, so the practice was images "need to work on mobile" regardless of the user's device. For those of us writing Angular and Ember (because React wasn't a thing yet), you had to legitimately render the correct src based on context you could get from JavaScript. {{#if browserSmal}} <img src="image-high-res.jpg" /> {{else}} <img src="image-med-res.jpg" /> {{/if}} This is back when we wrote handlebars for our markup and the web was filling up with SPAs with no server-side-rendering. We did it this way because HTML lacked a way for specifying how we wanted to optimize images. Then in 2012, RICG introduced 2 new specs for image optimization, with 2 different use cases: <picture> elements and srcset. Picture Elements I love the <picture> element. It gives us a lot of control

## Checkout Optimization: 15 Tactics to Boost Conversion Rates in 2026

DevFeed: [Checkout Optimization: 15 Tactics to Boost Conversion Rates in 2026](<https://devfeed.tech/articles/checkout-optimization-15-tactics-to-boost-conversion-rates-in-2026-9754.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/checkout-optimization/>)

Author: Ayush Agarwal

Published: 2026-04-04T00:00:00Z

Content type: article

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [web design](<https://devfeed.tech/topics/web-design.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3d](<https://devfeed.tech/tags/3d.md>), [account](<https://devfeed.tech/tags/account.md>), [apple-pay](<https://devfeed.tech/tags/apple-pay.md>), [bank](<https://devfeed.tech/tags/bank.md>), [billing](<https://devfeed.tech/tags/billing.md>), [card](<https://devfeed.tech/tags/card.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [chargebacks](<https://devfeed.tech/tags/chargebacks.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [churn](<https://devfeed.tech/tags/churn.md>), [co-founder](<https://devfeed.tech/tags/co-founder.md>), [collect](<https://devfeed.tech/tags/collect.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-products](<https://devfeed.tech/tags/digital-products.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [payments](<https://devfeed.tech/tags/payments.md>), [saas](<https://devfeed.tech/tags/saas.md>)

### AI overview

The article argues that checkout friction can be reduced through structural choices and targeted improvements across the payment flow. It favors overlay checkout for in-app SaaS upgrades, inline checkout for dedicated payment pages, and hosted checkout when quick integration matters most. Its tactics include removing prepayment account creation and unnecessary fields, offering local payment methods and currencies, showing trust signals and taxes before payment, supporting mobile wallets and clear 3DS flows, clarifying subscription terms, and tracking drop-off by step. It also recommends hiding coupon fields until requested, using webhooks for prompt post-payment access and confirmation, and testing pay-button wording and placement. The article presents Dodo Payments as providing overlay and inline checkout, localized methods, tax handling, and webhook support; these are vendor claims in the supplied text.

### Source excerpt

Learn 15 proven checkout optimization tactics that reduce cart abandonment and increase conversion rates for digital products and SaaS.

## GitHub Mobile now supports iOS 26 with refined visuals and smoother navigation

DevFeed: [GitHub Mobile now supports iOS 26 with refined visuals and smoother navigation](<https://devfeed.tech/articles/github-mobile-now-supports-ios-26-with-refined-visuals-and-smoother-navigation-72325.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2025-09-15-github-mobile-now-supports-ios-26-with-refined-visuals-and-smoother-navigation>)

Author: Allison

Published: 2025-09-15T10:43:31Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [iOS](<https://devfeed.tech/topics/ios.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [animations](<https://devfeed.tech/tags/animations.md>), [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [github](<https://devfeed.tech/tags/github.md>), [github-mobile](<https://devfeed.tech/tags/github-mobile.md>), [integration](<https://devfeed.tech/tags/integration.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-26](<https://devfeed.tech/tags/ios-26.md>), [layout](<https://devfeed.tech/tags/layout.md>), [liquid-glass](<https://devfeed.tech/tags/liquid-glass.md>), [manager](<https://devfeed.tech/tags/manager.md>), [motion](<https://devfeed.tech/tags/motion.md>), [multitasking](<https://devfeed.tech/tags/multitasking.md>), [native](<https://devfeed.tech/tags/native.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>)

### AI overview

GitHub Mobile's iOS 26 update refreshes the interface with Liquid Glass styling, a refined tab bar, restyled controls, and smoother transitions. Search, tab switching, and toolbars have been reorganized for quicker code access. Layouts adapt to portrait, landscape, and larger or windowed screens, including Stage Manager workflows. The release also adds larger touch targets, improved contrast, enhanced Dynamic Type support, and an app icon that adapts to light, dark, and tint modes. The update is rolling out on the App Store.

### Source excerpt

With support for iOS 26, GitHub Mobile adopts a refined visual language, smoother motion, and tighter system integration. This helps you move from idea to pull request more naturally across...

## How did we build 3D animations in mobile apps?

DevFeed: [How did we build 3D animations in mobile apps?](<https://devfeed.tech/articles/how-did-we-build-3d-animations-in-mobile-apps-15453.md>)

Original publisher: [Read original article](<https://medium.com/wise-engineering/how-did-we-build-3d-animations-in-mobile-apps-515c3de87b74?source=rss----f2565bbe9c46---4>)

Author: Yağız Gürgül

Published: 2025-01-29T16:59:35Z

Content type: article

Language: en

Sources: [Wise](<https://devfeed.tech/sources/wise-engineering-medium.md>)

Topics: [3D](<https://devfeed.tech/topics/3d.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [animation](<https://devfeed.tech/tags/animation.md>), [animations](<https://devfeed.tech/tags/animations.md>), [apps](<https://devfeed.tech/tags/apps.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-apps](<https://devfeed.tech/tags/mobile-apps.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [three-js](<https://devfeed.tech/tags/three-js.md>)

### AI overview

Wise chose three.js scenes rendered in local HTML files inside mobile web views to bring its 3D illustrations to life across iOS and Android. The team cited lower engineering effort than maintaining native solutions, stronger support and documentation, and WebGL performance; it reports 60/120 FPS across scenes on both platforms. Their models were built for static illustrations and were large: the plane glTF was about 19.3 MB and all supported scenes totaled around 324 MB. The excerpt begins an optimization approach that extracts embedded images to avoid duplicating shared textures, but ends before giving the full process or its results.

### Source excerpt

In March 2023, Wise launched its new brand -- as part of it, we introduced a collection of bold new 3D illustrations. While visually stunning, our brand team had bigger ambitions to bring them to life and elevate Wise further. This took us on a journey to understand the technical landscape and challenges around creating a seamless multi-platform solution for interactive 3D animations. interactive 3D intro on Wise iOS appThe new illustration set in Wise Our new illustration set took inspiration from icons, allowing us to communicate with a global audience. They're unique, bold and dynamic, even when still. They give us opportunities to share moments of delight with our customers and help our brand stand out from billboard to button. check out https://wise.design/ for more! What sets illustrations at Wise apart is that they're not static. Each one is paired with a crafted 3D model, featuring detailed UV maps, precise shading, and carefully designed lighting. This raises an exciting question: What if we rendered these illustrations dynamically in real time, making them interactive on mobile apps? Native or web view? To render illustrations in real time, we explored several technical solutions: Native Filament three.js We opted to create 3D scenes using three.js, one of the most popular open-source web projects. Some of the reasons behind this include: Managing native solutions for iOS and Android platforms would demand extra engineering effort. The support and documentation available for three.js surpass others. The web view solution delivers native-like performance by using WebGL on both platforms. As a result, we consistently achieve 60/120 FPS across all scenes on both devices. The plan was simple. Build simple HTML files that render 3D scenes and load these files locally in mobile apps 🚀 But we had a "huge" problem... The 3D models were specifically designed for static illustrations, resulting in a high polygon count that contributes to larger file sizes. For instance

## Redesigned Navigation Now Available to All Users

DevFeed: [Redesigned Navigation Now Available to All Users](<https://devfeed.tech/articles/redesigned-navigation-now-available-to-all-users-73325.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2023-10-17-redesigned-navigation-now-available-to-all-users>)

Author: Kevin Duck

Published: 2023-10-17T14:19:02Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [interactive web design](<https://devfeed.tech/topics/interactive-web-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [beta](<https://devfeed.tech/tags/beta.md>), [breadcrumbs](<https://devfeed.tech/tags/breadcrumbs.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code-search](<https://devfeed.tech/tags/code-search.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [github](<https://devfeed.tech/tags/github.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [links](<https://devfeed.tech/tags/links.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [responsive](<https://devfeed.tech/tags/responsive.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

GitHub's redesigned navigation is now enabled for all users following a beta that gathered user feedback. It adds breadcrumbs for location context, streamlined menus for repositories, teams, and workflows, and quick access to code search and the command palette. Issues and pull requests across a user's collection are available at the top navigation level. The update also includes accessibility and mobile responsiveness improvements, plus bug fixes; the text does not describe specific implementation details or limitations.

### Source excerpt

The redesigned GitHub navigation is now live for everyone! After a successful beta phase, which allowed users to test and provide feedback, we're confident in providing a more intuitive, responsive,...

## Screen response time. A critical metric for user experience

DevFeed: [Screen response time. A critical metric for user experience](<https://devfeed.tech/articles/screen-response-time-a-critical-metric-for-user-experience-37406.md>)

Original publisher: [Read original article](<https://medium.com/okcredit/screen-response-time-a-critical-metric-for-user-experience-fc2be922859f?source=rss----40ea5327aac7---4>)

Author: Anjal Saneen

Published: 2022-06-27T06:10:37Z

Content type: article

Language: en

Sources: [OkCredit](<https://devfeed.tech/sources/okcredit-medium.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Interaction to Next Paint](<https://devfeed.tech/topics/interaction-to-next-paint.md>), [lazy loading](<https://devfeed.tech/topics/lazy-loading.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [constraintlayout](<https://devfeed.tech/topics/constraintlayout.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [addition](<https://devfeed.tech/tags/addition.md>), [all](<https://devfeed.tech/tags/all.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-vitals](<https://devfeed.tech/tags/android-vitals.md>), [app](<https://devfeed.tech/tags/app.md>), [better](<https://devfeed.tech/tags/better.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [critical](<https://devfeed.tech/tags/critical.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experience](<https://devfeed.tech/tags/experience.md>), [metric](<https://devfeed.tech/tags/metric.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [okcredit](<https://devfeed.tech/tags/okcredit.md>), [screen](<https://devfeed.tech/tags/screen.md>), [time](<https://devfeed.tech/tags/time.md>), [user](<https://devfeed.tech/tags/user.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

OkCredit defines screen response time as the interval from a screen-opening tap to its first frame and argues for measuring it because Android vitals report slow and frozen frames but do not capture the full responsiveness picture. The article describes XML loading costs (I/O, parsing, reflective View creation, then measure/layout/draw) and says Compose avoids those costs but loads its classes on first use, making the first Compose screen slower than subsequent ones. It recommends aiming for 100 ms or less and profiling before optimizing. Reported steps include asynchronous inflation (which OkCredit says cut screen load time 25% and frozen-frame performance 30%), flattening layouts, moving long work off the main thread, lazy initialization, and Compose R8/baseline-profile checks. Custom views can reduce hierarchy and traversal costs but are harder to maintain; X2C may bring integration and APK-size costs. OkCredit reports that targeting 100 ms also reduced frozen frames by 40%, while cautioning that performance work should be iterative and stop when gains no longer justify effort.

### Source excerpt

A high-quality user experience is always a top priority at OkCredit. We aim to make the mobile app as fast as possible. To better understand performance impact, we measure various L1 and L2 metrics. Among them, a key metric is screen response time. The time it takes the user to reach the first frame of the screen after clicking for opening a screen. Screen response time is a core web metric for web pages. In addition, Google recently introduced a new metric for assessing full-page responsiveness on the web called Interaction to Next Paint. Android vitals are far behind in terms of measuring responsiveness metrics compared to the web. You can watch the state of responsiveness on the web here. Playstore vitals measure frozen frames and slow frames, but they don't tell the whole story about the responsiveness of the app. In order for your app to be responsive, you must derive multiple metrics yourself. We share our learnings and findings on-screen response time in this blog post. How the screens loads Let me explain briefly how a screen loads on Android before we move on to the metric. For optimal screen load, it's important that you understand all the operations that occur there. Please keep in mind the term Screen in Android terms as referring to a fragment or activity. We demonstrate the XML and jetpack compose individually below. XML We must first understand the principle of XML layout loading, If you dig deep into the Android source code of Activity.setContentView, each layout must go through inflation before it can pass the measure and be drawn. XML Layout load to draw Phases 1. Load and parse the XML file loadXmlResourceParser is the method responsible for loading an XML file. We wouldn't need to go into the implementation details of this method, we just need to know that it reads the XML file we wrote into memory, and performs some data parsing and encapsulation. Therefore, this is a method that requires I/O. As we know, I/O operations are typically more comput

## Forcing Grid Stacking with Bootstrap on Mobile

DevFeed: [Forcing Grid Stacking with Bootstrap on Mobile](<https://devfeed.tech/articles/forcing-grid-stacking-with-bootstrap-on-mobile-28132.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/bootstrap/2021/12/23/forcing-grid-stacking-with-bootstrap-on-mobile.html>)

Author: Fuzzygroup

Published: 2021-12-23T17:33:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Bootstrap](<https://devfeed.tech/topics/bootstrap.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [bootstrap](<https://devfeed.tech/tags/bootstrap.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [html](<https://devfeed.tech/tags/html.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [viewport](<https://devfeed.tech/tags/viewport.md>), [wrap](<https://devfeed.tech/tags/wrap.md>)

### AI overview

When a Bootstrap layout shrank on mobile instead of wrapping, adding `<meta name="viewport" content="width=device-width, initial-scale=1">` to the HTML `<head>` made it format as expected. The excerpt does not describe other causes or limitations.

### Source excerpt

I recently had the situation where a Bootstrap application: Worked perfectly on a desktop with a side by side layout Properly wrapped on desktop when the window was resized down to a mobile like form factor Failed to ever wrap on mobile showing just a smaller version of the desktop I puzzled over this quite a bit until I ran a google search for "bootstrap text too small on mobile" which led me to this directive: <meta name="viewport" content="width=device-width, initial-scale=1"> This needs to be inserted into your html head element and then, like magic, made everything format perfectly on mobile.

## Beyond Mobile First

DevFeed: [Beyond Mobile First](<https://devfeed.tech/articles/beyond-mobile-first-15546.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/beyond-mobile-first>)

Author: Ryan O'Neill

Published: 2021-11-04T09:00:00Z

Content type: article

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [web design](<https://devfeed.tech/topics/web-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [view transitions](<https://devfeed.tech/topics/view-transitions.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [animation](<https://devfeed.tech/tags/animation.md>), [animations](<https://devfeed.tech/tags/animations.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [commerce](<https://devfeed.tech/tags/commerce.md>), [component](<https://devfeed.tech/tags/component.md>), [css](<https://devfeed.tech/tags/css.md>), [design](<https://devfeed.tech/tags/design.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [e-commerce](<https://devfeed.tech/tags/e-commerce.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [gestures](<https://devfeed.tech/tags/gestures.md>), [google](<https://devfeed.tech/tags/google.md>), [haptics](<https://devfeed.tech/tags/haptics.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Square Online describes using its open-source Vue.js component library, Maker, to bring app-like interactions to the web. It enlarges tap targets, adds floating action bars with loading and success feedback, and uses modals to support mobile-first interactions across desktop and mobile, including layered dialogs. On mobile Safari, taps in roughly the bottom 44 pixels can reveal the browser bar instead of activating a site control; the article's workaround keeps action bars above that zone and uses CSS `safe-area-inset-bottom` to adjust spacing. The approach has limits: mobile websites cannot access some native APIs such as haptics and force touch, and smooth transitions across pages and layered modals are more complex than in native apps. The article points to a proposed browser transition API as a possible future improvement.

### Source excerpt

Bringing app-like experiences to the web

## Safari's 100vh Problem

DevFeed: [Safari's 100vh Problem](<https://devfeed.tech/articles/safari-s-100vh-problem-19122.md>)

Original publisher: [Read original article](<https://medium.com/rbi-tech/safaris-100vh-problem-3412e6f13716?source=rss----904782439303---4>)

Author: Jon Rose

Published: 2020-06-17T19:14:35Z

Content type: article

Language: en

Sources: [RBI Tech](<https://devfeed.tech/sources/rbi-tech.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [100vh](<https://devfeed.tech/tags/100vh.md>), [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [css3](<https://devfeed.tech/tags/css3.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [layouts](<https://devfeed.tech/tags/layouts.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [positioning](<https://devfeed.tech/tags/positioning.md>), [responsive](<https://devfeed.tech/tags/responsive.md>), [safari](<https://devfeed.tech/tags/safari.md>), [scrolling](<https://devfeed.tech/tags/scrolling.md>), [viewport](<https://devfeed.tech/tags/viewport.md>)

### AI overview

On mobile Safari, 100vh stays constant as the browser button bar hides and appears, so the bar can cover content positioned using viewport height. The article says Safari chose this behavior to avoid layout jank from a changing viewport. For a footer or navbar, it suggests positioning instead of using height. For content that gets cut off, it describes setting section heights to window.innerHeight after page load and updating them on resize; this works but can itself look janky as heights change. The article favors avoiding layouts that depend on content at the bottom of the viewport, while noting workarounds such as React's Div100vh and the tradeoff of working against the browser's behavior.

### Source excerpt

Safari, being an Apple product, tends to "Think Different". Given Apple's dominant market share, especially in the US, it's important that we understand these differences, and know how to work with them. In this blog post, we're going to tackle the 100vh problem. 100vh Quick recap. The vh unit, introduced with CSS3, allows you to specify the percent of the total viewport's height. So 100vh would be 100% of the viewport. It's mobile responsive and has made building layouts much easier. Navbar Problem Let's try making a simple homepage with a footer for navigation. https://medium.com/media/cff698e095a28a6928ff7148fc3c694d/href In the main element is our content. We give it a height of 95vh or 95% of the total height. The footer gets the remaining 5% of the viewport. If we load this up on a desktop, it works exactly as expected. Checking Safari on mobile and we see: Why? This must be a bug, right? Well, no. This is actually a feature. When working on Safari, the team worked hard to show the button bar only when necessary. Their goal was to give more space to the website whenever possible, which is why the button bar hides when scrolling. This lead to a tough decision about how the viewport's height would be handled. Would it: 1. change the height every time the bar hides and shows or 2. make the viewport height constant, and have the button bar cover part of the viewport They opted for a constant height to avoid jankiness. This means that our navbar is in fact there, just hidden behind the button bar. When the button bar hides, we can see the navbar really was there. Navbar Solution So what do we do? Instead of placing our navbar by using height, we use positioning instead. https://medium.com/media/20c4987011013a9c0c01fd1b0ce9aceb/href Checking it out on desktop and we can see nothing changed: And now on mobile, we finally get what we expect. Content Problem The navbar example is a bit contrived. Hopefully you wouldn't use height for positioning regardless of the 100vh

## Array 1.6.0

DevFeed: [Array 1.6.0](<https://devfeed.tech/articles/array-1-6-0-80660.md>)

Original publisher: [Read original article](<https://posthog.com/blog/the-posthog-array-1-6-0>)

Published: 2020-05-19T00:00:00Z

Content type: release

Language: en

Sources: [PostHog](<https://devfeed.tech/sources/posthog.md>)

Topics: [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>)

Tags: [1-6](<https://devfeed.tech/tags/1-6.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [alert](<https://devfeed.tech/tags/alert.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [array](<https://devfeed.tech/tags/array.md>), [cdp](<https://devfeed.tech/tags/cdp.md>), [context-layer](<https://devfeed.tech/tags/context-layer.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data-agents](<https://devfeed.tech/tags/data-agents.md>), [debug](<https://devfeed.tech/tags/debug.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [design](<https://devfeed.tech/tags/design.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [microsoft-teams](<https://devfeed.tech/tags/microsoft-teams.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

Array 1.6.0 adds resizable dashboards that can be rearranged on mobile, color customization, full-screen presentation mode and sidebar access to pinned dashboards. PostHog also documents how to send alerts to Microsoft Teams via webhook, and expands paths visualizations from page views to arbitrary sequences of page views or events. Performance work includes funnel rendering reported as ten times faster for users with many events, event partitioning to speed up trends and paths, and improved event insertion scalability. Stickiness breakdowns were temporarily removed because they were causing issues; the team says their return will depend on user feedback.

### Source excerpt

One of the most fun weeks we've had so far with our UX - resizable and touch-enabled dashboards with a new display mode, Microsoft Teams support, and...

## Responsive issue template chooser

DevFeed: [Responsive issue template chooser](<https://devfeed.tech/articles/responsive-issue-template-chooser-74921.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2019-04-03-responsive-issue-template-chooser>)

Author: Luke Hefson

Published: 2019-04-03T18:05:01Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [devices](<https://devfeed.tech/tags/devices.md>), [issue](<https://devfeed.tech/tags/issue.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-devices](<https://devfeed.tech/tags/mobile-devices.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [responsive](<https://devfeed.tech/tags/responsive.md>), [template](<https://devfeed.tech/tags/template.md>), [templates](<https://devfeed.tech/tags/templates.md>)

### AI overview

On mobile, people submitting a new issue to a repository with multiple issue templates are directed to a responsive template chooser.

### Source excerpt

When people on mobile devices want to submit a new issue to a repository which has multiple issue templates set up, they will now be directed to a responsive view...

## Responsive release pages

DevFeed: [Responsive release pages](<https://devfeed.tech/articles/responsive-release-pages-75070.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2018-08-14-responsive-release-pgs>)

Author: admin

Published: 2018-08-14T07:00:00Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [mobile](<https://devfeed.tech/tags/mobile.md>), [release](<https://devfeed.tech/tags/release.md>), [responsive](<https://devfeed.tech/tags/responsive.md>)

### AI overview

GitHub release pages are now responsive, allowing users to view, create, and edit repository releases and tags on mobile devices.

### Source excerpt

All release pages are now responsive. Easily view, create or edit your repository's releases and tags on a mobile device!

## Responsive search pages

DevFeed: [Responsive search pages](<https://devfeed.tech/articles/responsive-search-pages-75086.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2018-07-31-responsive-search-pgs>)

Author: admin

Published: 2018-07-31T07:00:00Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [mobile optimization](<https://devfeed.tech/topics/mobile-optimization.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devices](<https://devfeed.tech/tags/devices.md>), [for-devs](<https://devfeed.tech/tags/for-devs.md>), [github-com](<https://devfeed.tech/tags/github-com.md>), [guides](<https://devfeed.tech/tags/guides.md>), [marketplace](<https://devfeed.tech/tags/marketplace.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-devices](<https://devfeed.tech/tags/mobile-devices.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [pages](<https://devfeed.tech/tags/pages.md>), [responsive](<https://devfeed.tech/tags/responsive.md>), [search](<https://devfeed.tech/tags/search.md>), [technical](<https://devfeed.tech/tags/technical.md>), [technical-guides](<https://devfeed.tech/tags/technical-guides.md>), [tips](<https://devfeed.tech/tags/tips.md>), [wikis](<https://devfeed.tech/tags/wikis.md>)

### AI overview

GitHub's search pages are now responsive on mobile devices, allowing searches across code, topics, Marketplace, and wikis while navigating GitHub.com on any device.

### Source excerpt

All search pages are now responsive on mobile devices. This means you can search across code, topics, Marketplace, and wikis when navigating GitHub.com on any of your devices.

[Next page](<https://devfeed.tech/topics/mobile-optimization.md?cursor=WyIyMDE4LTA3LTMxVDA3OjAwOjAwKzAwOjAwIiwgIjZjMTM3NzVhLWVhNjktNGE4Zi1iMmE1LWNiYjExNDFkZGZkNiJd>)