# draggable Published articles for draggable. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Beyond the Luminance Ramp: A Shape-Aware ASCII Renderer in Three.js DevFeed: [Beyond the Luminance Ramp: A Shape-Aware ASCII Renderer in Three.js]() Original publisher: [Read original article]() Author: Edoardo Lunardi Published: 2026-09-04T15:01:38Z Content type: tutorial Language: en Sources: [Codrops]() Topics: [shape-aware rendering](), [ASCII art shader](), [Three.js shaders](), [Three.js custom shaders]() Tags: [3d](), [ascii](), [ascii-art-shader](), [ascii-dithering](), [ascii-shader](), [atlas](), [browser-based-ascii-renderer](), [creative-coding-three-js](), [custom-element-webgl](), [draggable](), [draggable-3d-logo](), [glsl-ascii-shader](), [glyph-atlas-rendering](), [glyph-matching-algorithm](), [gpu](), [gpu-ascii-rendering](), [gpu-glyph-search](), [interactive-ascii-art](), [luminance-ramp-alternative](), [procedural-ascii-art](), [real-time-ascii-rendering](), [shaders](), [shape-aware-ascii-renderer](), [shape-aware-rendering](), [three-js](), [three-js-ascii-renderer](), [three-js-custom-shaders](), [three-js-shader-tutorial](), [three-js-webgl](), [tutorials](), [webgl](), [webgl-ascii-art](), [webgl-post-processing](), [webgl-shader-tutorial]() ### AI overview A Three.js ASCII renderer improves on luminance-only glyph selection by sampling each character cell's shape and matching it against printable glyphs on the GPU. ### Source excerpt The Codrops mark, rebuilt as a draggable solid and printed in ASCII on the GPU, where every character cell searches 95 glyphs for its own. ## What's new in Postgres Managed by ClickHouse: RBAC, Terraform, ClickPipes, extensions, and more DevFeed: [What's new in Postgres Managed by ClickHouse: RBAC, Terraform, ClickPipes, extensions, and more]() Original publisher: [Read original article]() Author: Kaushik Iska Published: 2026-06-18T16:10:49Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Authorization](), [Terraform](), [API](), [Model Context Protocol](), [Monitoring](), [Replication](), [stripe](), [draggable]() Tags: [api](), [clickhouse](), [draggable](), [management](), [mcp](), [metrics](), [monitoring](), [postgres](), [replication](), [rest-api](), [stripe](), [terraform](), [update](), [visualization]() ### AI overview This update covers new capabilities for Postgres managed by ClickHouse, including fine-grained per-service access control, a redesigned console, Terraform support, MCP support, Stripe integration, monitoring improvements, and a read-replica topology view. ### Source excerpt Postgres managed by ClickHouse's first major update since public beta, covering fine-grained access control, a redesigned console, Terraform support, MCP integration, Stripe provisioning, migrations, billing, and capacity reservations -- all shipped in und ## Building the Crossplay Board DevFeed: [Building the Crossplay Board]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2026-06-08T16:46:30Z Content type: tutorial Language: en Sources: [New York Times]() Topics: [Android](), [Development](), [Jetpack Compose](), [Mobile](), [ui](), [screen](), [real-time]() Tags: [android](), [android-app-development](), [asynchronous](), [code](), [compose](), [development](), [draggable](), [jetpack-compose](), [kotlin](), [mobile](), [multiplayer](), [real-time](), [screen]() ### AI overview The New York Times Games team describes building the Android game board for Crossplay, a multiplayer word game with a 15x15 grid, draggable tiles, real-time animation, and asynchronous matches. The team used a hybrid architecture: an Android GridLayout with 225 tile Views integrated into surrounding Jetpack Compose UI. ### Source excerpt How We Made a 15X15 Game Surface Feel at Home on AndriodIllustration by Lehel Kovács By Shafik Quoraishee What Is Crossplay? The New York Times Games team has been building daily puzzles for quite a while: Wordle, Spelling Bee, Connections, The Mini. These are solo games. The player opens them, solves them, and then closes them. This leads to a simple, satisfying experience which delights millions of players a day. Crossplay is an altogether different endeavor. It's the first multiplayer game from NYT Games, and it brings a friend (or a stranger) into the experience with them. So two players, one board, in real time. In Crossplay, players take turns placing letter tiles on a 15x15 grid to form interlocking words, but built for mobile with a focus on speed, fairness, and the back-and-forth tension that compels the player to play one more round. The matches are asynchronous by default. The player makes their move, the opponent gets notified and responds when they're ready. But the board animates as if the players are both sitting at the same table. When we set out to build it, we knew the board would be the hardest part. While the networking, the opponent matching, and the game logic were all challenging work, the board itself which is part of the core game loop was the most difficult piece because of the number of interactions required to make it function correctly, in concert. Since every cell is a potential drop target and every tile is draggable, the board needs to respond instantly to touch *and* animate their opponent's moves *as they happen*. This all must occur on a screen that is a few inches wide. In this post we discuss what it took to get that right on Android. Starting with the Grid One of our first questions was architectural. How should 225 tiles be laid out? Jetpack Compose is the obvious modern choice. But Crossplay's development started before our team had fully migrated to Compose, and the game board had specific requirements that made a pure-Compos ## Building a Google Maps Style Bottom Sheet with Jetpack Compose DevFeed: [Building a Google Maps Style Bottom Sheet with Jetpack Compose]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-02-15T07:34:23Z Content type: tutorial Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Jetpack Compose](), [Android](), [ui]() Tags: [android](), [bottomsheet](), [compose-multiplatform](), [dialog](), [draggable](), [jetpack-compose](), [kotlin-multiplatform](), [state](), [ui]() ### AI overview This tutorial explains how to build a Google Maps-style bottom sheet with Jetpack Compose using FlexibleBottomSheet. It covers three expansion states, non-modal interaction, state-dependent content, programmatic transitions, nested scrolling, and dynamic content sizing. ### Source excerpt Google Maps popularized a bottom sheet pattern that most Android developers recognize immediately: a small panel peeking from the bottom of the screen, expandable to a mid height for quick details, and draggable to full screen for comprehensive information. The user interacts with the map behind the sheet at all times. This pattern looks simple on the surface, but implementing it correctly requires solving several problems: multi state anchoring, non modal interaction, dynamic content adaptation, and nested scroll coordination. Jetpack Compose's standard ModalBottomSheet only supports two states (expanded and hidden) and blocks background interaction with a scrim, making it unsuitable for this use case. In this article, you'll explore how to build a Google Maps style bottom sheet using FlexibleBottomSheet, covering how to configure three expansion states with custom height ratios, how to enable non modal mode so users can interact with the content behind the sheet, how to adapt your UI dynamically based on the sheet's current state, how to control state transitions programmatically, how to handle nested scrolling inside the sheet, and how to wrap content dynamically for variable height sheets. Why ModalBottomSheet falls short Consider the standard Material 3 bottom sheet: https://medium.com/media/8a38f40dd78c91260a666308710000ce/href This gives you two states: expanded and hidden. The sheet covers the background with a scrim, blocking all interaction behind it. For a confirmation dialog or action menu, this is fine. But for a Google Maps style experience, you need: Three visible states: A peek height showing a summary, a mid height for details, and a full height for comprehensive content. No scrim: The map behind the sheet must remain fully interactive. Dynamic content: The content should adapt based on the current expansion state. Nested scrolling: Scrollable content inside the fully expanded sheet should scroll naturally, and dragging down from the top of the scro ## Make your site interactive with code layers DevFeed: [Make your site interactive with code layers]() Original publisher: [Read original article]() Author: Alex Mullans Published: 2025-06-17T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Code](), [React](), [AI Chat](), [Canvas](), [Web](), [shaders](), [draggable]() Tags: [ai](), [code](), [component](), [design](), [developer](), [draggable](), [features](), [figma](), [generate](), [react](), [shaders](), [tool](), [web](), [website-design](), [workflow]() ### AI overview Figma introduces code layers for Figma Sites, enabling users to add custom React-powered interactions and motion to website designs. Users can create or convert components into code layers, use Figma's AI chat to build and refine behavior, edit code directly, and generate variations for comparison on the canvas. ### Source excerpt Today we're launching code layers--a new way to build custom interactions in Figma Sites. ## How to Drag and Drop in React DevFeed: [How to Drag and Drop in React]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2024-10-10T04:56:46Z Content type: tutorial Language: en Sources: [Robin Wieruch]() Topics: [React](), [Tutorial](), [draggable](), [Library]() Tags: [component](), [container](), [draggable](), [how-to](), [npm](), [react](), [react-component](), [react-dnd](), [react-drag-and-drop](), [state](), [tutorial]() ### AI overview A step-by-step React tutorial for building vertical and horizontal drag-and-drop lists with @hello-pangea/dnd. It covers stateful items, reusable components, Droppable and Draggable components, and reordering list state after drag events. ### Source excerpt A tutorial about using Drag and Drop in React by example for a vertical list (later horizontal list) with @hello-pangea/dnd as DnD library ... ## Listening for element events with Compose for Web - Gustavo Fão Valvassori DevFeed: [Listening for element events with Compose for Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2024-01-26T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-for-web](), [Web](), [draggable](), [Kotlin]() Tags: [browser](), [compose-for-web](), [compose-multiplatform](), [css](), [draggable](), [event](), [kotlin](), [kotlin-js](), [kotlin-multiplatform]() ### AI overview This tutorial explains how to handle HTML element events in Compose for Web. It covers common event listeners, updating composable state from clicks and input changes, and using side effects to implement more complex behavior such as a draggable window. ### Source excerpt In a declarative world, events are the main way to interact with the elements, and most components have a way to listen for them. ## Making Your React Native Gestures Feel Natural DevFeed: [Making Your React Native Gestures Feel Natural]() Original publisher: [Read original article]() Author: Andrew Lo Published: 2023-01-20T18:37:05Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [React Native](), [draggable](), [Mobile](), [React UI animations](), [App]() Tags: [animation](), [app](), [draggable](), [mobile](), [react-native]() ### AI overview This article explains how to make draggable React Native interfaces feel more natural. Using a Shop app Sheet component, it shows how incorporating drag velocity, position, spring animations, elasticity, and resistance can improve gesture feedback and transitions. ### Source excerpt When working with draggable elements in React Native mobile apps, there are some simple ways to help gestures and animations feel better and more natural. ## Simplifying Drag and Drop (Lists and Nested Lists) DevFeed: [Simplifying Drag and Drop (Lists and Nested Lists)]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2022-09-05T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [JavaScript](), [draggable](), [Web Development]() Tags: [components](), [debug](), [drag-and-drop](), [draggable](), [how-to](), [javascript](), [react]() ### AI overview This tutorial shows how to simplify drag-and-drop lists and nested lists in JavaScript by extracting reusable components around a drag-and-drop library. It includes demos for basic lists and moving categories or items between nested categories. ### Source excerpt I always forget how to use any drag and drop library until I have to use it again. Currently, the one I've been working with is , the... ## Swipe to reveal in Jetpack Compose DevFeed: [Swipe to reveal in Jetpack Compose]() Original publisher: [Read original article]() Author: Denys Rudenko Published: 2021-02-19T17:21:58Z Content type: tutorial Language: en Sources: [Stories by Denis Rudenko on Medium]() Topics: [Jetpack Compose](), [Compose](), [draggable](), [ui]() Tags: [android](), [androiddev](), [compose](), [compose-animation](), [draggable](), [gestures](), [jetpack-compose](), [stateflow](), [swipe-to-reveal](), [viewmodel]() ### AI overview A tutorial showing how to implement swipe-to-reveal cards in Jetpack Compose by detecting horizontal drag gestures and managing revealed card state with a view model and StateFlow. ### Source excerpt Swipe to dismiss is really easy to implement in compose, including item removal animation by using a combination of SwipeToDismiss & AnimatedVisibility composables. SwipeToDismiss doesn't allow us to stop the dragging motion midway though, so let's take a look how we can achieve the following by detecting horizontal drag gestures on any composable. https://medium.com/media/1a355b2d3e397414c51442342f16cda5/hrefStep 1: Creating a data source Those who've read expandable lists in jetpack compose can skip this step, since data source is almost the same. First we define our model to hold the card related info: data class CardModel(val id: Int, val title: String) We'll be using AAC viewModel example here, but feel free to use any "controller" abstraction you prefer. https://medium.com/media/28ca457093268969ac4f2e179ee860ef/href This class serves 5 purposes: Holds list of cards using MutableStateFlow in _cards field, and exposes a StateFlow to observers via cards field. Holds list of "revealed" card ids in _revealedCardIdsList, and exposes them to observers via revealedCardIdsList field. Provides list of cards using getFakeData() function. We need a coroutine here, to emit the testList into _cards. Has onItemExpanded() to mark cards as revealed, by adding tapped card id to _revealedCardIdsList, and notify observers about this change by mutating the state of _revealedCardIdsList. Has onItemCollapsed() to remove revealed card id from _revealedCardIdsList, and notify observers about this change by mutating the state of _revealedCardIdsList. Step 2: CardsScreen composablehttps://medium.com/media/4505fde17b0e8f9672f392cb9b3296f3/href We are observing the viewModel.cards containing our list of cards, and viewModel.expandedCardIds with the help of .collectAsStateWithLifecycle(). UI is quite simple here, each list item is represented with a Box that contains our hidden action icons & the draggable card. ActionsRow -- row with 3 icons, exposes callbacks from each icon tap: onDelete, ## Creating Native Components That Accept React Native Subviews DevFeed: [Creating Native Components That Accept React Native Subviews]() Original publisher: [Read original article]() Author: Joe Redridge Published: 2020-02-25T15:30:00Z Content type: tutorial Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [React Native](), [Android](), [Kotlin](), [Material Design](), [Gradle](), [TypeScript](), [cross-platform]() Tags: [android](), [cross-platform](), [design](), [draggable](), [google](), [gradle](), [guide](), [how-to](), [kotlin](), [react-native](), [typescript]() ### AI overview A guide to building an Android native bottom sheet component for React Native that can render and interact with React Native views inside the sheet. It covers project setup, Kotlin, TypeScript, Gradle dependencies, and exposing the native component through a new package. ### Source excerpt This guide will show you how to make a native component that provides bottom sheet functionality to React Native and renders React views inside.