Responsive Design Guidelines

When “progress” hurts usability I recently updated my phone with One UI 7 system and suddenly… everything felt unfamiliar. The call screen, the buttons, the menus - all had shifted. What used to be muscle memory (where to press “mute”, how to check quick settings, where to glance for notifications) suddenly became a little puzzle I had to solve each time. For me, it was just inconvenient and frustrating. But then I thought: 👉 What about someone with low vision who depends on consistent icon placement? 👉 Or someone with motor difficulties, who now has to stretch or swipe differently? 👉 Or someone who struggles with cognitive load and relies on predictability? But let's look closer at such questions. Scientific studies show that when icons are moved, resized, or placed differently across screens, people, especially those with low vision, take longer to find them, make more errors, or feel more strain. 1️⃣ Evaluating visual consistency of icon usage across devices A study from Zhejiang University looked at how icons are scaled across devices, how their spacing, size, border shape etc. change. They found that when these visual properties aren’t consistent, user perception is negatively affected — users find it harder to process the icon sets, especially when moving between devices/screens (the link: https://lnkd.in/ePQ8fMbk) 2️⃣ Influence of icon semantics & visual search performance (eye-tracking study) Another study demonstrates that icons that are semantically familiar (that is, the picture suggests clearly what it does) + consistent layouts help people find them faster. When icon familiarity is low, or icons are placed inconsistently (e.g. different positions, different visual density), performance & accuracy drop (the link: https://lnkd.in/efYgWf84) 3️⃣ Low vision users in graphical user interface interaction This study compared people with normal vision to people with low vision using GUI interfaces (in this case home appliance control panels). It found that people with low vision have particular problems when controls are too close together (distance), text is small, contrast is low. Also layout consistency (distance between elements, consistent positioning) matters a lot (the link: https://lnkd.in/eGb8y4K7) That’s when “progress” stops being progress. A sleek new look might impress on the surface, but if it hides information, increases effort, or breaks familiar patterns, it’s not really helping people. And every time, the people most affected are those already facing accessibility barriers. Progress should mean more inclusion, not less. I work as a web accessibility specialist, I help teams make sure their updates don’t create new obstacles and I’d be glad to help review and fix accessibility issues. #a11y #inclusion #webaccessibility #webdesign

Introducing the Agent-to-User Interface by Google 🔥 A2UI lets your AI agents generate native, interactive UIs on the fly. And it's 100% Open Source. Here's the problem with AI chat interfaces: They hit the ceiling fast. User: "Book me a flight to Tokyo" Agent: "Here are 47 options with dates, prices, layovers, seat classes..." walls of text...walls of text Nobody wants to parse that. You want buttons. Cards. Filters. A real interface. But hardcoding UIs for every possible agent action? Impossible. A2UI flips the entire paradigm. Your agent doesn't just respond with text. It streams native UI components directly to the user. Flight cards. Booking forms. Interactive carousels. Date pickers. Generated on the fly. Rendered instantly. Zero client-side code changes. Here's how it works: 🔌 Built on A2A Protocol Secure transport layer. Your agent streams JSONL payloads describing UI intent. 🏗️ Truly Framework-Agnostic Write once. Render on React, Flutter, Android, Web Components. Any surface. ⚡ Real-Time Streaming Progressive rendering as the agent thinks. No waiting for complete responses. 🔒 Secure by Design Clean separation of structure and data. UI injection risks mitigated. The old way: User navigates menus → Clicks through forms → Waits for confirmations The A2UI way: User asks → Agent streams the exact interface needed → User acts immediately Chat interfaces were step one. Generative UI is step two. Stop building static dashboards that gather dust. Start letting your agents build the UI. This is Day 15 of 25 in Google Cloud's Advent of Agents. Missed previous days? The archive is live. Catch up anytime. ♻️ Repost to share this free and interactive course with your network. And follow this space to stay updated for what's to come.

Your customer is everywhere, → scrolling on Instagram,  → searching on Google,  → watching on YouTube,  → chatting on WhatsApp. If your brand’s message isn’t consistent across platforms, here’s what happens: - Customers get confused. - Trust diminishes. - Engagement drops. --- Cross-platform branding ensures your message is cohesive, no matter where your audience interacts with you. It’s not about copying and pasting content, it’s about tailoring your voice and visuals while staying true to your core identity. Why it works: 💗 Builds Recognition: Consistency makes your brand memorable. 💗 Fosters Trust: Familiarity breeds loyalty. 💗 Drives Engagement: A seamless experience keeps customers coming back. --- Imagine this: A customer sees your ad on Instagram, clicks through to your landing page, receives a follow-up email, and watches your explainer video, all with the same tone, visuals, and clear message. That’s the power of cross-platform branding. Here's some examples of brands nailing this: - Netflix: Consistent storytelling across social media, email, and in-app experiences. - Nike: Seamless integration of their “Just Do It” ethos, from YouTube ads to Twitter responses. --- Here’s what you can do to be like them: 1️⃣ 𝗔𝘂𝗱𝗶𝘁 𝗬𝗼𝘂𝗿 𝗕𝗿𝗮𝗻𝗱 𝗣𝗿𝗲𝘀𝗲𝗻𝗰𝗲 Identify inconsistencies across platforms and align your visuals, tone, and messaging. 2️⃣ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗮 𝗨𝗻𝗶𝗳𝗶𝗲𝗱 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆 Map out how each platform contributes to the customer journey and connect the dots. 3️⃣ 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗧𝗼𝗼𝗹𝘀 𝗳𝗼𝗿 𝗖𝗼𝗵𝗲𝘀𝗶𝗼𝗻 Platforms like Hootsuite and Canva make it easier to manage branding across multiple channels. 4️⃣ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗣𝗲𝗿𝘀𝗼𝗻𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻 Tailor messages to each platform while keeping your brand identity intact. 5️⃣ 𝗠𝗲𝗮𝘀𝘂𝗿𝗲 & 𝗥𝗲𝗳𝗶𝗻𝗲 Use analytics to understand what works where, and continuously optimize. --- In a world where customers jump between platforms,  your brand’s consistency is what makes it unforgettable. Cross-platform branding isn’t just a strategy — it’s the NOW of customer engagement. --- PS: Ready to make your brand’s message consistent and impactful everywhere your audience is? Let’s create a strategy tailored to your goals. Connect with me today! 🚀

You Saw That Ad on Your Phone… But Bought It on Your Laptop, Right? 💡 Welcome to the fascinating world of Cross-Device Targeting, one of the most quietly powerful tools in digital advertising. It’s not magic, and it’s not just retargeting, it’s about recognizing that people move between devices constantly, and designing smarter ad experiences around that behavior. Let’s break it down: 🔄 It’s 11 PM. You’re scrolling through Instagram on your phone. You spot a sleek coffee machine. Intriguing.. but not tonight. Next morning, you’re back at your desk, logged in on your work laptop. Same product. Different format. Right timing. This time? You click. You buy. ☕ That, in essence, is cross-device targeting done right, treating the customer journey as one continuous experience, not a series of disconnected screens. Why does this matter? • We don’t make decisions on the first click. • Attention spans are short. Devices are many. • Consistency across platforms = Trust + Recall. Pro Tips for Marketers? ▪️ Customize creatives based on device type. → Keep it swipeable on mobile, detailed on desktop. ▪️ Set up frequency caps across devices. → Avoid bombarding the user on every screen they own. ▪️ Use sequential messaging. → Storytelling that unfolds, not repeats, across screens. ▪️ Measure cross-device conversions, not just last-click. → Your attribution model should evolve with your customer behavior. Got a “cross-device moment” where you bought something after seeing it on multiple devices? Share your story below! 👇 #DigitalMarketing #ProgrammaticAdvertising #CrossDeviceTargeting #CustomerJourney #MarketingTips #AdTech

Stop building apps for just one screen. 🛑 If your app doesn't talk to the tablet, the watch, or the car sitting in the driveway, you aren’t just behind the curve—you’re losing users. We’ve all been there: struggling with messy Bluetooth handshakes, Wi-Fi Direct protocols, and the nightmare of cross-device authentication. Google just simplified the game with the Cross-Device SDK. Here is why this is a massive shift for the Android ecosystem: 🚀 The "Abstraction" Magic Instead of wrestling with low-level connectivity (Bluetooth, Wi-Fi, UWB), the SDK provides a unified toolkit. You focus on the experience; the SDK handles the "how." 📱 Personal vs. Communal Experiences Personal: Start an article on your phone, finish on your tablet. Seamless. Communal: Group food ordering or multiplayer gaming without the "pass the phone" dance. 🛠️ Core Capabilities: Device Discovery: Find nearby devices without the permission headaches. Secure Connections: Encrypted data transfers out of the box. Multi-device Sessions: Move or share app states instantly. The Strategist’s Take: This isn't just a technical update; it’s a UX revolution. The most successful apps of 2025 and beyond will be the ones that feel "ubiquitous"—existing wherever the user happens to be looking. What’s the biggest "cross-device" friction point you face as a user today? Let’s discuss below. 👇 #AndroidDev #MobileDevelopment #GoogleSDK #SoftwareEngineering #TechTrends

One of the common interview questions in system design rounds is how to build reusable UI components that can work across frameworks. And, this is where 𝗪𝗲𝗯 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 come into picture. 𝗪𝗲𝗯 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 are a set of browser native APIs that allow us to create custom, reusable HTML elements without relying on frameworks. 𝗪𝗲𝗯 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 are made of 4 main specifications: 𝟭. 𝗖𝘂𝘀𝘁𝗼𝗺 𝗘𝗹𝗲𝗺𝗲𝗻𝘁𝘀 This is how we define our own tags like <𝙪𝙨𝙚𝙧-𝙢𝙤𝙙𝙚𝙡>. We can manage the logic using lifecycle callbacks: • 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱𝗖𝗮𝗹𝗹𝗯𝗮𝗰𝗸: This is called when component is inserted in DOM. • 𝗱𝗶𝘀𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱𝗖𝗮𝗹𝗹𝗯𝗮𝗰𝗸: This is called when component is removed from DOM. • 𝗮𝘁𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗖𝗵𝗮𝗻𝗴𝗲𝗱𝗖𝗮𝗹𝗹𝗯𝗮𝗰𝗸: This is called when a prop or attribute is changed/ added/ removed from DOM. 𝟮. 𝗦𝗵𝗮𝗱𝗼𝘄 𝗗𝗢𝗠 This gives us a private, scoped DOM tree. We use it so our CSS doesn't leak and break the rest of the app layout, and global styles do not affect our internal component structure. 𝟯. 𝗛𝗧𝗠𝗟 𝗧𝗲𝗺𝗽𝗹𝗮𝘁𝗲𝘀 We can use the <template> tag to define HTML that doesn't render immediately. 𝟰. 𝗘𝗦 𝗠𝗼𝗱𝘂𝗹𝗲𝘀 This is a standard way in which we can package and share our components across different projects. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: If you open YouTube and try to inspect, you can find multiple custom elements inside DOM.

Your app is beautiful— But does it work on every device? (You’d be surprised how many don’t.) I once worked with a startup. → Their UI was stunning. Animations. Colors. Wow factor. But within weeks, users started dropping. → The app crashed on tablets. → Lagged on older Androids. → Buttons overlapped on iPhones. Design wasn’t the problem. → Performance and compatibility were. It’s been 4 years since that project. → But I still get referrals from them. Why? Not because I fixed bugs. → Because I cared enough to test what users actually used. → Because I didn’t just make it “look” good—I made it “work” everywhere. People don’t care about features they can’t use. → They care if it loads. → If it flows. → If it makes their life easier. Because at the end of the day… ✦ People don’t remember your code. ✦ They remember how your app made them feel. ✦ Frustrated—or frictionless. Want loyal users? → Test where it matters. → Don’t assume one-size fits all. Cross-device testing isn’t extra work— → It’s respect for your user. P.S. Tired of seeing low retention?  "I’m ready to build what people stay for."

Part 2: More from “TJ Plays with AI + Design Systems.” This time: Figma MCP → Web Components → React Storybook → Custom UI Generator. I took the same banner component from yesterday’s demo (https://lnkd.in/g6yt7rNw), generated from Figma using the official MCP server and pushed the workflow further: ✅ MCP server got us 95% of the way there (some missed tokens, but easy fix) ✅ Wrapped the Web Component in React ✅ Automated drop it into our React-flavored Storybook ✅ Connected it to our custom Story UI Generator ✅ Now, PMs, designers, and basically any non-devs can customize layouts without writing a line of code What’s wild is how fast we’re moving from design intent to actual usable, testable, customizable UI, without needing a dev in the loop at every step. The gap between design and dev is getting smaller. But this shows the gap between dev and product is closing too! 🙌 Demo video below 👇 Would love to hear what others are doing with MCP and generative UIs.

A Deep Dive into Cross-Device Tracking with BigQuery: Analyzing GA4 IDs 🔍 Understanding the cross-device journey of users is crucial in today’s multi-device world. By analyzing GA4 identifiers in BigQuery, you can track users across mobile, desktop, and tablet interactions, giving you a full picture of the customer journey across devices. Here’s how to leverage GA4’s Client ID and User ID for meaningful insights into user behavior: 1. GA4’s User Identifiers: Client ID and User ID: GA4 automatically generates a client ID and assigns it to a user’s device or browser, allowing for device-specific tracking. If your app or website has a login system, you can set up a user ID, which creates a single identifier for users across devices when they’re logged in. 2. Bringing GA4 Data to BigQuery for Cross-Device Analysis: Export your GA4 data to BigQuery to access and merge data by Client ID and User ID. This allows for deep, customizable analysis not available in the GA4 UI. 3. Querying Cross-Device Data with SQL: Write an SQL query to track a user’s journey across devices using Client ID and User ID. And let the query identify unique users by their User ID. 4. Mapping the Customer Journey Across Devices: By combining Client ID (device-level) and User ID (user-level), you can see how users interact with your brand across different devices. For example, a user might start on mobile, research further on a tablet, and make a final purchase on a desktop. Tip: Segment users by device type to understand which devices contribute to each stage of the funnel, from awareness to conversion. 5. Identifying Drop-Offs and Key Conversions Across Devices: Once you have a map of user interactions across devices, write an SQL query in your BigQuery console to analyze where drop-offs occur and which device is most frequently used for conversions. This will provide insights into device behavior at different stages 6. Visualizing the Cross-Device Journey for Stakeholders: Present your findings in Looker Studio or Tableau with visualizations that highlight device-specific engagement, drop-offs, and conversions. Tip: Use flowcharts or Sankey diagrams to show how users move between devices before conversion, making it easy for stakeholders to grasp cross-device trends. What are the benefits of Cross-Device Tracking in BigQuery? By analyzing Client ID and User ID in BigQuery, you gain: ✓ A holistic view of customer journeys across devices, helping you understand user behavior better. ✓ Insight into which devices contribute to which stages of the journey, allowing you to optimize multi-device experiences. ✓ Data to improve personalized marketing and device-specific strategies. Understanding cross-device journeys can be a game-changer in today’s digital world! #DigitalAnalytics #BigQuery #GA4 #CrossDeviceTracking #SQL #WebAnalytics #CustomerJourney #DataScience #UserExperience

In a perfect world, your network state would be synchronized, deterministic, and always aligned with intent. In the real world, especially at hyperscale, the network is often a distributed system under stress, and inconsistent state is not just a possibility… it’s inevitable. An inconsistent network state leads to: - Unexpected blackholes - Intermittent reachability issues - Operational confusion during incidents So we’ve learned not to ask if it will happen. Instead, we ask: “How quickly can we detect, isolate, and correct it?” What we mean by “Inconsistent Network State”... network “state” exists across: - Device configs - Control plane databases (RIB, FIB, LSDB, etc.) - BGP session views across reflectors - Route policy enforcement points - Intent pipelines (what should be) - Actual device telemetry (what is) Any mismatch across these layers creates inconsistency! Common causes of inconsistency: - Partial deployment: config push failed mid-stream - Out-of-band edits: someone made a change outside the pipeline - Asynchronous convergence: different devices learn routes at different times - Control plane partitioning: e.g., BGP RR cluster split - Undetected drift: config rollback or override happened without orchestration awareness Even worse: these inconsistencies are often invisible until something breaks! How we handle it at scale: 1. State comparison engines (Intent vs. Reality) We continuously compare: - Desired state (from GitOps/intent pipelines) - Live state (from API, CLI, or telemetry) - Derived state (e.g., BGP tables, route-map effects) Every delta is analyzed: 🔄 Legitimate in-progress change ⚠️ Drift due to failure ❌ Misconfiguration or error 2. Multi-layer consistency validation We validate across: - Control plane views (e.g., RIB-to-RIB comparisons) - Data plane outcomes (ping/trace/testflow probes) - Policy propagation (prefix tags, labels, communities) - Interface and adjacency states (L2/L3) 3. Atomic deployments and rollbacks We moved away from piecemeal config pushes. Every change is: - Rendered as a complete policy or intent block - Validated as a unit - Deployed transactionally or rolled back entirely 4. Consistency-aware observability We built pipelines to track: - Prefix propagation time per region - Drift between FIBs and intended route sets - Stale/aged state in control plane databases - Asymmetry scores for traffic flows 5. Corrective reconciliation loops If inconsistency is detected: - Auto-reapply config (if safe) - Trigger reconciliation PR - Isolate the device or fabric block - Alert engineering with diff output and recommended action What this solves: 🕒 Reduces time-to-detect for silent failures 🔄 Fewer “unknown cause” routing anomalies 🧠 Improves confidence during deploys and rollbacks ✅ Stronger policy enforcement consistency across devices and regions