# navigation Navigation is the science and practice of determining and controlling position, course, and direction, including Internet navigation supported by domain names and DNS infrastructure. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## New AI technique could make minimally invasive surgeries safer and more precise DevFeed: [New AI technique could make minimally invasive surgeries safer and more precise]() Original publisher: [Read original article]() Author: Adam Zewe | MIT News Published: 2026-09-16T15:00:00Z Content type: news Language: en Sources: [MIT AI News]() Topics: [Artificial Intelligence](), [AI Research](), [3D](), [navigation]() Tags: [3d](), [ai](), [artificial-intelligence](), [computer-science-and-artificial-intelligence-laboratory-csail](), [computer-science-and-technology](), [computer-vision](), [electrical-engineering-and-computer-science-eecs](), [health-care](), [images](), [imaging](), [jameel-clinic](), [machine-learning](), [medical-devices](), [medical-imaging](), [minimally-invasive-surgery](), [mit-ibm-computing-research-lab](), [mit-schwarzman-college-of-computing](), [model](), [national-institutes-of-health-nih](), [navigation](), [paper](), [polina-golland](), [precision](), [real-time](), [research](), [school-of-engineering](), [vision](), [vivek-gopalakrishnan]() ### AI overview MIT researchers and collaborators developed xvr, an AI method that adapts to individual patients and rapidly aligns intraoperative X-rays with preoperative 3D medical scans. The technique is intended to improve surgical navigation for minimally invasive procedures. ### Source excerpt This patient-specific method, called xvr, helps doctors use X-rays for surgical navigation in fields such as orthopedics and neurosurgery. ## What is the Super key in Omarchy? DevFeed: [What is the Super key in Omarchy?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-09-11T09:52:11Z Content type: tutorial Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [navigation](), [Cheat sheet](), [configuration](), [Terminal](), [App]() Tags: [cheat-sheet](), [commands](), [faq](), [shortcuts](), [terminal](), [vim](), [windows]() ### AI overview This tutorial explains that Omarchy uses the Super key as the primary modifier for system navigation and shortcuts. It describes ten shortcut categories, including launching applications, closing windows, opening a terminal, changing layouts, viewing keybindings, navigating windows, switching workspaces, and moving windows between workspaces. ### Source excerpt In Omarchy, the Super key acts as the primary modifier key for almost all system navigation and shortcuts, functioning as the Windows key on standard keyboards or the Command key on a Mac layout Based on standard Omarchy configurations and recent Hyprland window manager defaults, here are the top 10 essential Super key combinations you need to know for ... ## Scaling llms.txt with a Hierarchy of Files DevFeed: [Scaling llms.txt with a Hierarchy of Files]() Original publisher: [Read original article]() Author: Kyan Yang Published: 2026-09-01T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [navigation](), [Website]() Tags: [agents](), [context-window](), [documentation](), [engineering](), [files](), [generation](), [navigation]() ### AI overview Mintlify rebuilt llms.txt generation as a hierarchy of files to keep large documentation sites within the 100,000-character limit while preserving access to pages. In tests across 200 tasks on ten documentation sites, the improved version completed tasks 52.1% faster and used 44.8% fewer tokens. ### Source excerpt Large documentation sites were hitting Mintlify's 100,000-character llms.txt limit and omitting pages. We rebuilt generation as a hierarchy of files so agents can reach every page without loading the entire index. ## Match Compose injection scopes to real UI ownership DevFeed: [Match Compose injection scopes to real UI ownership]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Compose](), [ui](), [navigation](), [Process]() Tags: [compose](), [lifecycle](), [navigation](), [screen](), [ui]() ### AI overview This tutorial explains how to align Compose injection scopes with actual UI ownership and lifecycle events. It distinguishes object retrieval from creation, discusses process, navigation-destination, request, and feature-session lifetimes, and recommends testing both retention and exit behavior. ### Source excerpt Compose makes it easy to request an object close to the UI that uses it. Proximity is useful, but it does not define ownership. Recomposition can call a function many times. Navigation can keep or discard a back-stack entry. The operating system can recreate the process. A sound scope names the event that owns the object. Separate retrieval from creation Ask two questions for each injected object: Where is the object retrieved? Which lifecycle creates and releases it? A repository retrieved by a composable can still be process-scoped. A screen model can be owned by a navigation destination. A transient formatter can be created for each request. Write the lifetime next to the definition and test that the object survives, or does not survive, the intended event. ## Make scalable routing system for your Flutter Apps DevFeed: [Make scalable routing system for your Flutter Apps]() Original publisher: [Read original article]() Author: Kanan Yusubov Published: 2026-07-29T15:25:43Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Routing (disambiguation)](), [navigation](), [modules](), [Dependency injection](), [Usability]() Tags: [clean-architecture](), [dependency-injection](), [flutter](), [go-router](), [modular-router](), [modules](), [navigation](), [router](), [routing](), [routing-system](), [usability]() ### AI overview This tutorial describes a scalable, decoupled routing system for Flutter apps. It explains a wrapper built on go_router that adds typed route arguments, native and path parameters, cross-module modularization, nested routes, presentation modes, and type-safe route guards. ### Source excerpt Recently, I've been working on migrating our app's routing system. We previously used auto_route, but eventually realized its tightly coupled nature made it incredibly difficult to scale across independent modules. Furthermore, its heavy reliance on code generation became a bottleneck for our workflow. To resolve this, we decided to architect a clean, scalable, and highly decoupled routing system. Our new solution is a powerful wrapper built on top of go_router. It abstracts away the raw string navigation and supercharges the router with custom features to maximize usability and type safety. In this blog post, I will walk you through the core benefits of this new routing system, covering the following key topics: Unified Routing Protocol (AppRouteInfo) Strictly Typed Route Arguments Native & Path Parameters Support Cross-Module Modularization (AppModuleRouter) Hierarchical Back stack & Sub-Routes (Nested Route Definitions, Decoupled Cross-Module Navigation) Dynamic Presentation Modes (e.g., Native, ModalSheet, NoTransition) Guard Interceptor Mechanism (Type-Safe Redirects, Global Interceptors) Note: This blog will show the general usage and problems it solved. For more detailed code, you can check the following link: https://github.com/thisisyusub/scalable-routing-system-demoArchitectural Structure of Routing System Here is how the demo application is structured to achieve a fully decoupled, scalable routing system: scalable_routing_system_demo (main app): The entry point of the application responsible for wiring up all services, dependency injection, and global route configurations. app_routes: Houses all route definitions, parameters, routing protocols, and models to ensure fully type-safe navigation. This is decoupled from the core routing package to separate app-specific business needs from generic routing mechanics. routing_system (core router): A generic, domain-agnostic router package that has zero knowledge of the app's specific routes. It exclusively provid ## jetc.dev Newsletter Issue #322 DevFeed: [jetc.dev Newsletter Issue #322]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-14T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [compose-for-desktop](), [multiplatform](), [Android](), [navigation]() Tags: [android](), [compose](), [compose-for-desktop](), [compose-multiplatform](), [dev](), [jetpack-compose](), [module](), [navigation]() ### AI overview This newsletter issue rounds up recent Jetpack Compose developments and related community content, including Compose updates, TV Compose performance, navigation, filter bars, settings-screen DSLs, Compose Multiplatform with SwiftUI, and Compose for Desktop performance. ### Source excerpt SubcomposeLayout! TV Compose! Nav3! Filter bars! Setting screens! And... can we make Compose for Desktop better?!? ## Documentation team funding 2026 DevFeed: [Documentation team funding 2026]() Original publisher: [Read original article]() Author: Infinisil Published: 2026-07-11T14:11:06Z Content type: news Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Documentation](), [Nix](), [Deployment](), [CI/CD](), [Framework](), [navigation]() Tags: [2026](), [announcement](), [announcements](), [documentation](), [funding]() ### AI overview The NixOS Foundation announces renewed fundraising for its documentation team. The effort aims to improve onboarding, discovery, framework evaluation, the docs.nixos.org cutover, continuous deployment, feedback times, navigation, and redirects. It also invites non-monetary support through community channels and meetings. ### Source excerpt tl;dr: There is a renewed effort to improve documentation, head to Documentation team - Open Collective or contact foundation@nixos.org to chip in with funding! With the 2023 crowd-funding in documentation funding, we've seen some improvements, but a lot more is needed to make significant progress towards improving the overall experience with Nix documentation, including onboarding and discovery. Especially newcomers frequently struggle with our documentation, get frustrated and notice gaps, and have a hard time adopting Nix. In addition, in the Nix community survey 2025 we see that most people want excess funding to be allocated to improving documentation. While the NixOS Foundation doesn't have that much excess funding, @hsjobeki has stepped up to pick up leadership of the documentation team with support by @friedow. While they're volunteering their own time to lead the team, they'd like to have access to funding for not just ensuring that stuff gets done, but also maintained over time. They've collaborated to agree on a documentation vision (initial announcement) to work towards. For that reason, we're asking individuals and companies to donate to the renewed documentation team OpenCollective, so that we can reach the funding goals (more details on OpenCollective): (1.000 EUR /month) Paid documentation maintainer (4.000 EUR ) Framework evaluation (15.000 EUR ) Prepare docs.nixos.org cutover (8.000 EUR ) Continuous deployment & Reduce feedback times (8.000 EUR ) Navigation & redirects If a company is interested in providing a significant amount of funding and would like a contract and invoice, please reach out to foundation@nixos.org. Furthermore, if you'd like to support documentation in non-monetary ways, feel free to join the Matrix channel and/or bi-weekly meetings (see "Nix documentation meeting" in the NixOS Calendar), or see where you can help from updates in the discourse category. -- NixOS Foundation board 8 posts - 5 participants Read full topic ## jetc.dev Newsletter Issue #321 DevFeed: [jetc.dev Newsletter Issue #321]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-07T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [navigation](), [multiplatform](), [ui]() Tags: [compose](), [compose-multiplatform](), [dev](), [migration](), [navigation](), [newsletter](), [ui](), [updates]() ### AI overview Jetc.dev Newsletter Issue #321 reviews recent Jetpack Compose updates, including bug fixes and library releases, Nav3 migration experiences, a new 2D layout component, theme-aware Maps for Compose, Compose Multiplatform migration, and other Compose UI developments. ### Source excerpt Compose stable and beta updates! Nav3 migrations! Grid! Effects! And GLFW for Compose for Desktop?!? ## Coding Challenge #125 - Online Diff Viewer DevFeed: [Coding Challenge #125 - Online Diff Viewer]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-07-04T08:01:27Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [coding](), [web applications](), [Algorithm](), [Accessibility](), [Syntax Highlighting](), [navigation](), [CSS](), [HTML](), [JavaScript]() Tags: [accessibility](), [algorithm](), [browser](), [build](), [code](), [coding](), [css](), [html](), [javascript](), [navigation](), [syntax-highlighting]() ### AI overview Coding Challenge #125 asks readers to build an online diff viewer in the browser. The project compares two text inputs, computes a line-level diff, and presents additions, deletions, and unchanged lines, with planned features including multiple views, syntax highlighting, navigation, export, and accessibility. ### Source excerpt This challenge is to build your own online diff viewer. ## New chip could help tiny robots traverse complex environments DevFeed: [New chip could help tiny robots traverse complex environments]() Original publisher: [Read original article]() Author: Adam Zewe | MIT News Published: 2026-06-23T04:00:00Z Content type: news Language: en Sources: [MIT AI News]() Topics: [Hardware](), [Algorithms](), [3D](), [navigation](), [real-time](), [Green Software](), [Computer science]() Tags: [3d](), [aeronautical-and-astronautical-engineering](), [algorithms](), [artificial-intelligence](), [assembly](), [augmented-and-virtual-reality](), [autonomous-vehicles](), [computer-chips](), [computer-science-and-technology](), [efficiency](), [electrical-engineering-and-computer-science-eecs](), [energy](), [energy-efficiency](), [gleanmer](), [hardware](), [inside](), [laboratory-for-information-and-decision-systems-lids](), [low-power](), [machine-learning](), [memory](), [mit-schwarzman-college-of-computing](), [national-science-foundation-nsf](), [navigation](), [peter-zhi-xuan-li](), [real-time](), [research](), [research-laboratory-of-electronics](), [robotics](), [school-of-engineering](), [sertac-karaman](), [system-on-a-chip](), [trajectory-planning](), [vivienne-sze](), [zih-sing-fu]() ### AI overview MIT researchers developed a low-power chip that combines an efficient mapping algorithm with dedicated hardware to generate detailed 3D maps for robot navigation in real time. The system-on-a-chip uses about 6 milliwatts and is intended for tiny autonomous robots and other battery-limited devices. ### Source excerpt Researchers combined an efficient algorithm with dedicated hardware to rapidly generate 3D maps for navigation using minimal memory and power. ## Preventing Cypress Test Failures When Reloaded Elements Detach from the DOM DevFeed: [Preventing Cypress Test Failures When Reloaded Elements Detach from the DOM]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-06-17T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Document Object Model (DOM)](), [navigation]() Tags: [blog-post](), [component](), [cypress](), [demo](), [how-to](), [navigation](), [products](), [repo](), [testing](), [verify]() ### AI overview This tutorial explains why Cypress end-to-end tests can fail when client-side navigation updates the page after a command has found an element. It demonstrates how delayed rendering can leave an old element attached to the test subject and recommends waiting for the expected component or DOM state before continuing the command chain. ### Source excerpt Have you ever encountered end-to-end test error "... failed because the page updated as a result of this command, but you tried to c ## Adding Navigation support to Large Content Viewer with Compose DevFeed: [Adding Navigation support to Large Content Viewer with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-02-28T04:26:46.364000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [navigation](), [Compose](), [keyboard](), [screen](), [Code]() Tags: [code](), [compose](), [keyboard](), [navigation](), [screen](), [test]() ### AI overview This tutorial explains how to add keyboard and assistive-technology navigation to a large content viewer built with Jetpack Compose. It presents an approach using focus handling to show item previews, covers keyboard and screen reader navigation, and discusses voice access support. The author notes that the example is a demo and should be tested with users of assistive technologies before production release. ### Source excerpt In my previous blog post, Beyond Font Scaling: Large Content Viewer with Compose, I explained how to build a large content viewer from iOS using Jetpack Compose. The implementation did not include support for keyboard or other assistive tech navigation, so this blog post tackles those topics. A disclaimer: The way I'm presenting the support for assistive tech navigation in this blog post is one approach, and my goal is to provide examples and context, but as always, this is a demo project. In your production app, things might get a bit more complicated, and you might need to handle more variables. So always remember to test the solution, ideally with your users who use assistive technologies. And I hope it goes without saying: Before releasing to production. In this blog post, I'm presenting code for keyboard and screen reader navigation, then sharing some considerations for voice access support. The code relies heavily on the code presented in the previous blog post, so if you have questions about it, please check that post. A link for the full code is also provided at the end of the blog post. Keyboard Navigation Support The pointer input implementation presented in the previous blog post relies on long-press, but keyboard navigation doesn't support that kind of interaction, so we need another tactic to display the item preview. With a keyboard, focusing on an item is a natural choice, so we're going to use that. The idea is that when a user who navigates with a keyboard or a keyboard-emulating device focuses on a bottom bar item for the same duration as a long press, we will show the item preview. We can do this with the following code: NavigationBarItem( modifier = Modifier .onFocusChanged { if (it.isFocused) { scope.launch { delay( viewConfiguration.longPressTimeoutMillis ) previewedItem = item } } else { previewedItem = null } }, ... } We use the onFocusChanged-modifier. Its state indicates whether the current element is focused via it.isFocused. If it is, we ## Crafting a Perfect Product Catalog DevFeed: [Crafting a Perfect Product Catalog]() Original publisher: [Read original article]() Author: Shashank Khatri Published: 2026-01-29T11:33:26Z Content type: article Language: en Sources: [Bazaarvoice]() Topics: [data](), [clients](), [trust](), [navigation]() Tags: [apis](), [categories](), [conversations-api](), [data](), [file](), [format](), [ids](), [integration](), [navigation](), [product](), [product-catalog](), [reviews](), [source-of-truth](), [ugc]() ### AI overview This Bazaarvoice post presents best practices for maintaining product catalogs used to manage and display user-generated content such as ratings and reviews. It covers precise product names, consistent category information, and naming conventions for product and category identifiers to support integration, content submission, navigation, and accurate review associations. ### Source excerpt Your product catalog is the definitive source of truth for your online presence, especially when managing User-Generated Content (UGC) like ratings and reviews. For Bazaarvoice clients, a meticulously maintained catalog is vital for seamless integration and flawless display. This post explores three key best practices--from precise product naming and consistent category data to optimal naming conventions--that will unlock the full potential of your UGC program, drive trust, and boost conversions. ## How I built our knowledge base in an afternoon DevFeed: [How I built our knowledge base in an afternoon]() Original publisher: [Read original article]() Author: Anahita Sahu Published: 2026-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Information Architecture](), [Markdown](), [navigation]() Tags: [best-practices](), [documentation](), [information-architecture](), [knowledge-base](), [markdown](), [navigation]() ### AI overview A Mintlify team member describes migrating internal documentation from multiple platforms into a knowledge base using Mintlify's assistant, Slack, and the web editor. The workflow handled formatting and page placement, while the editor supported real-time navigation and information architecture changes. ### Source excerpt Migrating content from multiple sources to Mintlify and building a knowledge base in hours, not weeks. ## 10 UI fixes I shipped in 10 days DevFeed: [10 UI fixes I shipped in 10 days]() Original publisher: [Read original article]() Author: Dmytro Tovstokoryi Published: 2025-12-01T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [ui](), [User experience (UX)](), [User interface design](), [Accessibility](), [navigation](), [dashboards]() Tags: [accessibility](), [dashboards](), [engineering](), [interaction](), [keyboard](), [layout](), [navigation](), [ui](), [ux]() ### AI overview A Mintlify design engineer describes 10 UI improvements shipped over 10 days, addressing layout shifts, dynamic number widths, dropdown animation origins, input focus behavior, navigation interactions, and keyboard accessibility. ### Source excerpt Little details are what make UX so good you don't notice it. ## Using Navigation 3 with Compose Multiplatform DevFeed: [Using Navigation 3 with Compose Multiplatform]() Original publisher: [Read original article]() Published: 2025-11-15T00:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [compose-multiplatform](), [navigation](), [Compose](), [Google](), [Kotlin](), [ui]() Tags: [adaptive](), [compose-multiplatform](), [google](), [kmp](), [kotlin](), [material3](), [multiplatform](), [navigation](), [ui]() ### AI overview A tutorial on using Navigation 3 with Compose Multiplatform in a shared Kotlin Multiplatform project. It covers dependencies, back-stack-based navigation, route mapping, and adaptive list/detail layouts using Material3 Adaptive Navigation3. ### Source excerpt Navigation 3 is a new Compose based navigation library from Google that's designed with ease of use and flexibility in mind. ## Designing a Digital New York Times Museum DevFeed: [Designing a Digital New York Times Museum]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-10-15T18:30:40Z Content type: article Language: en Sources: [New York Times]() Topics: [digital](), [Requirements](), [navigation]() Tags: [archive](), [design](), [employees](), [intern](), [navigation](), [product](), [product-design](), [remote](), [requirements](), [sessions]() ### AI overview Five product design interns describe designing a proof-of-concept virtual museum that brings The New York Times' internal museum to remote employees. The article covers their research, requirements, user flows, navigation, onboarding, and artifact-page design. ### Source excerpt How five product design interns created an award-winning virtual museum experience for employeesIllustration by Lucas Burtin By Nuoran Chen, Mina Chung, Frannie Ello, Christina Su, and Bella Rinne A key element of The New York Times Product Design Internship Program is a cohort project where all the interns work as a group to create a deliverable that is presented to the entire product design team. We, the summer 2024 cohort, were tasked with designing a proof-of-concept that brings the internal company museum in the NYC office to remote employees. The Times Museum is home to multiple artifacts where visitors can freely roam from each display to understand how their stories intertwine. From an official letter authorizing the publication of the leaked Pentagon Papers to physical effects of our war correspondents, each display is unique and speaks to the history behind The Times' mission to bring independent journalism to all. Our group began our work with a tour of The Times Museum led by retired journalist and museum curator, David W. Dunlap. On this tour, David guided us through each artifact in chronological order, describing the stories behind each piece and additional facts that were not fully captured with labels. His guided tour was essential for understanding the details behind The New York Times history and journalistic evolution. This tour informed two key requirements for the virtual museum. A guided tour with pathways for autonomous exploration: Visitors should experience the museum in order as it was curated while also being able to explore independently. Highlight important artifacts: We want to reduce the cognitive load for visitors and prominent artifacts so visitors are not overwhelmed when they enter the virtual museum. With these defined requirements, we began the design process. We held multiple brainstorming sessions to prioritize features and propose user flows in this virtual museum, but quickly found ourselves at a roadblock. For many weeks, w ## Exploring Navigation 3 for Jetpack Compose DevFeed: [Exploring Navigation 3 for Jetpack Compose]() Original publisher: [Read original article]() Author: hitherejoe Published: 2025-08-29T08:31:25Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [navigation](), [Jetpack Compose](), [Android]() Tags: [android](), [dependencies](), [jetpack-compose](), [navigation](), [ui]() ### AI overview This tutorial explores Navigation 3 for Jetpack Compose, explaining its back-stack model, automatic UI updates, scoped state retention, adaptive layouts, and parent-child communication. It also covers setup and dependencies while noting that Navigation 3 is still in alpha. ### Source excerpt When working with Navigation in modern Android apps, we've utilised navigation graphs through the navigation libraries. While the move to compose made things simpler, we still needed to work with navigation graphs and work with complex approaches that were carried over from the original navigation libraries. Navigation 3 aims to simplify the task of adding... Continue reading -> ## Exploring Material 3 for Compose: Large Top App Bar DevFeed: [Exploring Material 3 for Compose: Large Top App Bar]() Original publisher: [Read original article]() Author: hitherejoe Published: 2025-08-04T14:59:31Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Compose](), [navigation]() Tags: [android](), [android-app-development](), [android-apps](), [android-development](), [androiddev](), [app-development](), [compose](), [how-to](), [implement](), [jetpack-compose](), [jetpackcompose](), [material-design](), [mobile-app-development](), [navigation](), [screen](), [state](), [visibility]() ### AI overview This tutorial explains how to use and customize Material 3's LargeTopAppBar composable in Compose. It covers the app bar's expanded and collapsed states and the scroll behaviors that control its transitions. ### Source excerpt In the last post, we took a look into the new Loading Indicator in the Material 3 expressive package. As we continue to dive into different parts of Material 3 we'll discover more components that we can plug into our apps. Up next we have the LargeTopAppBar - this composable brings dynamic, scroll-responsive navigation to... Continue reading -> ## Galileo Testing Exposed Communication and Reliability Concerns DevFeed: [Galileo Testing Exposed Communication and Reliability Concerns]() Original publisher: [Read original article]() Published: 2025-05-28T11:50:00Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [reliability](), [communications](), [navigation](), [digital]() Tags: [communication](), [digital-autonomy](), [gnss](), [infrastructure](), [navigation](), [partner](), [reliability]() ### AI overview The article argues that Galileo is important independent European navigation infrastructure but criticizes the EU and EUSPA for poor communication about service testing and disruptions. It describes outdated data being transmitted during a test and says the lack of explanation confused professional users. ### Source excerpt When Galileo (the European satellite navigation system) was proposed there was a lot of criticism. "We already have the US GPS", and we'd always be able to rely on our historical partner to take care of us. The US very much also said this. Yet, the EU persevered and now we have an independent worldwide navigation capability. And given recent developments, I think we can be well pleased that we don't have to rely on the US, China or Russia for this vital need! ## How a transitive dependency caused unexpected Android behavior DevFeed: [How a transitive dependency caused unexpected Android behavior]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2025-01-14T00:00:00Z Content type: opinion Language: en Sources: [Posts on Marco Gomiero]() Topics: [Android](), [Library](), [issue tracker](), [navigation]() Tags: [android](), [bugs](), [debugging](), [dependencies](), [fragments](), [issue-tracker](), [libraries]() ### AI overview The author recounts debugging a crash affecting some Android users and tracing unexpected behavior to a change introduced by an external library. The article advises checking library changes and transitive dependencies during updates. ### Source excerpt This article is just a short "rant" and a "therapy session" to remind and warn my future self. I was recently debugging a weird crash affecting some users. The issue was related to navigation, fragments, and backstacks. After weeks spent trying to reproduce it, reading online reports, and cross-referencing previous libraries and SDK updates, I finally had an illuminating moment after reading about a similar behavior in the Google Issue Tracker. It made me wonder: Could something have changed in the Android Manifest? ## Mintlify redesigns its dashboard with a new design system and improved user experience DevFeed: [Mintlify redesigns its dashboard with a new design system and improved user experience]() Original publisher: [Read original article]() Author: James Baduor Published: 2024-04-16T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [User interface design](), [Design system](), [Usability](), [User Experience](), [Authentication](), [navigation](), [Web Development]() Tags: [authentication](), [design](), [design-system](), [navigation](), [redesign](), [tailwind-css](), [usability](), [user-experience]() ### AI overview Mintlify describes a dashboard redesign centered on a complete design system overhaul, simplified visual styling, improved navigation, progressive disclosure, and additional authentication options. The article also covers onboarding and settings-page changes informed by customer feedback, with further customization and component improvements planned. ### Source excerpt At Mintlify, we understand that design goes beyond aesthetics; it's about creating experiences that delight and empower users. Industry leaders like Linear, Vercel, Airbnb, and Apple have set a high standard, demonstrating that exceptional design is not merely a bonus but a critical factor in achieving success. ## Tiamat -- simple Compose Multiplatform navigation DevFeed: [Tiamat -- simple Compose Multiplatform navigation]() Original publisher: [Read original article]() Author: Yahor Urbanovich Published: 2024-02-29T12:52:22Z Content type: tutorial Language: en Sources: [Stories by Yahor Urbanovich on Medium]() Topics: [compose-multiplatform](), [navigation](), [Compose](), [multiplatform](), [Library]() Tags: [compose](), [compose-multiplatform](), [demo](), [developers](), [multiplatform](), [navigation](), [open-source]() ### AI overview This tutorial introduces Tiamat, an open-source navigation library for Compose Multiplatform. It explains the authors' requirements, including instance-based navigation without string keys, state saving, arbitrary data passing, no code generation, and no dependency on a specific architecture. It also begins demonstrating setup and usage. ### Source excerpt generated by Bing image creatorTiamat - simple Compose Multiplatform navigationIntro Why do we need another navigation library? You can say: just choose one of the existing solutions. For our project initially, we have chosen the Google Navigation Compose library. It was quite simple for developers who still migrated their minds to the new "Compose world". For some time we made a wrapper around the navigation library, to simplify access to the Navigation controller from any Compose screen. LocalNavController returns the current controller in composition Despite various improvements in navigation, we had a lot of critical moments that did not satisfy us: Navigation using String key A difficult way to pass data between screens Navigation only over replace We have experimented with some other libraries: Voyager -- it doesn't update very often (recently got status 1.0), no possibility to pass lambda as a parameter (issue) Decompose -- a too complex framework for our project. By the way, I use it on personal projects and recommend to try 🌚 other solutions overengeenered (by our opinion) Our requirements To reach a goal, we first need to understand what we are striving for. Here is what we expect from the navigation library: Compose first support + Multiplatform Simple API: Screeen creation, back stack handle, add/replace methods Navigation using Screen instance without any String keys A simple way to save State of the screen Pass Any data types between screens (even lambdas) and deliver the result Without code generation Without tying to any architecture or existing frameworks Welcome Tiamat We were so impressed with our internal library that we decided to make it open-source for Compose community. After several months of experiments and polishing the code we fit all our requirements above. Let's deep dive into code examples. Also, we have created a demo multiplatform App to demonstrate all current features. Please checkout the repository 🌚iOS, Desktop, Android sampleHow t ## Simplifying Navigation in Multi-Module Android Apps with Compose Destinations DevFeed: [Simplifying Navigation in Multi-Module Android Apps with Compose Destinations]() Original publisher: [Read original article]() Published: 2023-12-21T16:27:04Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [navigation](), [Android](), [Jetpack Compose](), [modules](), [Gradle]() Tags: [android](), [compose-destinations](), [gradle](), [jetpack-compose](), [kotlin](), [modules](), [navigation]() ### AI overview A Meetup engineering blog explains how its Android apps use Compose Destinations to implement navigation across Compose modules while avoiding legacy modules. It describes type-safe navigation, data-return handling, Gradle and KSP setup, and a simpler alternative to complex nested navigation graphs. ### Source excerpt In the world of Android development, we are often judged by the company and the app libraries we choose to keep. Our journey at Meetup, developing both the "Meetup" and "Meetup for Organizers" apps, [Next page]()