Tactile Sensing · Research Map

Making Touch Cheap: How One Open Tactile Sensor Grew a Research Tree

A guided tour of Awesome FlexiTac — what happens to a research field when a dense tactile sensor stops costing six hours and a thousand dollars, and starts costing three minutes and a few dollars.

Binghao Huang· August 12, 2026· ~15 min read· Jump to the ecosystem browser ↓

Most tactile-sensing papers end with a working demo and a sensor nobody else ever builds. That was the problem I ran into in 2023, and the reason this post exists: the bottleneck in tactile robot learning was never really the algorithm — it was access.

Three years later there is a small ecosystem of work built on the same open, flexible, low-cost tactile sensor. Awesome FlexiTac is the list. This post is the map: how the line started, which questions split off from it, who is working on what, and which branches are still wide open.

30
works tracked
20
built on FlexiTac
25+
institutions
$1.36
per sensor, at 1k units
Contents
  1. The access problem, not the algorithm problem
  2. Building from principle: V1 → V2
  3. Question 1 — can a policy actually use dense touch?
  4. The fusion question, and why naive concatenation fails
  5. Question 2 — where does tactile data come from?
  6. Question 3 — can simulation supply the rest?
  7. The research tree
  8. What this sensor is not good for
  9. Seven open problems
  10. Start in an afternoon
  11. Browse the ecosystem

1 · The access problem

In 2023 you could buy a dense tactile array. You could not buy the fifth revision of one.

The science already existed. MIT's scalable tactile glove — 548 sensors on a knitted glove, Nature 2019 — identified objects from recorded human grasps, offline.[1] Whether a policy could close a control loop on that signal is a different question, and in 2023 answering it began with a purchase order rather than an experiment.

There were three channels. Commercial research systems sold a calibrated array for roughly $1,000, but not its geometry. Factories were cheap in stock shapes and quoted me about $6,000 of non-recurring engineering per custom design. Academic prototypes moved by request — sometimes unavailable, sometimes licensed — leaving a hand rebuild of the 2019 glove at about 6 hours per sensor. Each is optimised, correctly, for a customer who is not an iterating robot-learning lab. Iteration was nobody's product.

So I went back to the physics: a resistive sandwich — polyimide film, adhesive, a force-sensitive resistive layer, and conductive traces crossing in a grid, with each crossing acting as one 3 mm² pressure unit. No cleanroom, no exotic materials. What was missing was iteration on manufacturability, which is not a publishable result. The gap was supply, not science.

Fabrication time per sensor hand-built v0 6 h FlexiTac V1 30 min FlexiTac V2 3 min 120× faster · V2 arrives from a PCB factory, so assembly is the only manual step Cost per sensing pad commercial ~$1,000 V1 (in-lab) ~$5 V2 (20 units) $4.19 V2 (1k units) $1.36
Figure 1. The access collapse. Bars are on a linear scale, which is the point — the drop is large enough that a log axis would flatter it. A three-order-of-magnitude change in cost and a 120× change in build time are not incremental improvements to a sensor; they change who is allowed to do the research at all.

2 · Building from principle

V1 was made by hand. V2 is made by a PCB factory.

Two versions matter for reading the rest of this map, because papers in the tree below build on one or the other.

FlexiTac V1FlexiTac V2
Fabrication~30 min, hand-made in lab~3 min assembly
Cost~$5 / piece$4.19 / piece (20 units)
$1.36 / piece (1,000 units)
CustomizationCut and layer by handChange the PCB file, reorder
Lead time~30 min, in-lab< 1 week, manufacture + ship
Used by3D-ViTac, Intelligent-Carpet-era workTouch in the Wild, VT-Refine, and most 2026 works

The honest chronology matters here, so let me state it plainly: the sensor existed as a lab artifact for roughly two years before it existed as a release. 3D-ViTac (CoRL 2024) ran on hand-built V1 pads. The FlexiTac hardware paper and open-source release came later, once V2 made the thing reproducible by someone who is not me.[2] The research came first and the product came second, which is the opposite of how these stories are usually told.

Thin, flexible, sensitiveBends around a curved surface without losing per-taxel response.
Full readout stack32 × 16 reading board, flat flex cable, Arduino-class MCU.
Figure 2. The hardware the rest of this map stands on. Everything here is open: fabrication repo, project page, paper.

3 · Question 1

Can a policy actually use dense touch?

This is where the research line starts, and it is why this map begins at 3D-ViTac (CoRL 2024) rather than at the earlier glove and carpet work.[3] Prior dense-tactile papers asked what can we infer from touch? 3D-ViTac asked the harder question: does adding touch make a manipulation policy better?

The uncomfortable early finding — one worth stating because it is easy to hide — is that naively adding tactile input often makes policies worse. The two signals are structurally mismatched. Vision is high-dimensional and global; touch is low-dimensional and local. Concatenate a 16×16 pressure array onto a visual embedding and the network learns to ignore it, or worse, overfits to it.

3D-ViTac's answer was to stop treating touch as a separate modality and put it in the same geometric space as vision: project each active taxel into 3D as a colored point, and hand the policy a single unified visuo-tactile point cloud. Tactile readings become part of the scene rather than a side-channel. A PointNet++ encoder and a diffusion policy consume the merged cloud.

3D-ViTac bimanual setup with tactile pads and a unified visuo-tactile point cloud
Unified 3D representation3D-ViTac · CoRL 2024 — taxels projected into the same cloud as the RGBD scene.
Force control on fragile itemsTactile-Reactive Gripper · npj Robotics 2026 — an active palm regulating grasp force.
Recovery under perturbationPolicy Consensus · ICRA 2026 — a human disturbs the object mid-task.
In-hand state when occludedVTAP Gripper · IROS 2026 — fingertip plus palm sensing during re-orientation.
Figure 3. Four capabilities dense touch unlocks — one drawn from each corner of the tree in §7, so the clips are attributed to their own papers rather than to 3D-ViTac. The common thread is what matters: every one is a case where vision is structurally unable to observe the quantity the policy needs — contact force, contact location under occlusion, or the moment a grasp starts to fail. 3D-ViTac's own four task suites (occluded fragile grasping, in-hand state, recovery, bimanual coordination) are in its project video.

4 · The fusion question

Two answers, and the field has not picked one

If touch has to be fused rather than appended, where in the stack should fusion happen? Two families have emerged from this line, and they make genuinely different bets.

Click to compare
Multi-view RGBD point cloud Tactile array 16 × 16 per finger Proprioception Unified 3D visuo-tactile cloud one geometric space PointNet++ shared encoder Diffusion policy action chunk 3D-ViTac · CoRL 2024 — geometry does the aligning needs calibrated cameras + known sensor pose
Figure 4. Two fusion strategies. A aligns modalities geometrically, before the policy sees them — precise, but it requires calibrated cameras and a known sensor pose, which you only have on a fixed rig. B aligns them statistically, inside a pre-trained encoder with bidirectional cross-attention — looser, but it survives hand-held data collection where nothing is calibrated. Downstream works in the tree split roughly along this line, and I do not think the question is settled.
A useful test when you read a visuo-tactile paper: ask where fusion happens and what it assumes. If the answer is "concatenated at the policy input," be suspicious of the ablation — that is the setting where touch most often fails to help, and where a tactile-free baseline is hardest to beat honestly.

5 · Question 2

Where does tactile data come from?

Vision-language-action models ride on internet-scale image and text data. There is no internet of touch. Every tactile frame that exists was collected by someone with a sensor on a robot — which, before the cost collapse in Figure 1, meant almost no frames existed at all.

Touch in the Wild (NeurIPS 2025) attacks this on the hardware side: take the robot out of the loop entirely.[4] A hand-held gripper with a fish-eye camera, two FlexiTac pads, and a 23 Hz reading board, carried around by a person. No robot, no lab, no calibration rig. That produced 2,700+ videos across 43 manipulation tasks — hardware stores, kitchens, student lounges, a Chipotle, campus outdoors — which then pre-trains the cross-attention encoder from Figure 4B before fine-tuning on a small number of robot demos.

In-the-wild captureHand-held, un-calibrated, 43 tasks in real environments.
WT-UMITactile UMI extending the idea to force-supervised humanoid data.
LeFlexiTacThe sensor wired into the LeRobot stack, so the data path is standard.
Figure 5. Scaling touch in the real world means decoupling data collection from robot time. The portable-device pattern is now the dominant strategy in this branch of the tree.

6 · Question 3

Can simulation supply what the real world cannot?

Portable capture scales coverage — many tasks, many scenes. It does not scale precision. For tight-tolerance contact-rich tasks, like inserting a peg into a hole with sub-millimetre clearance, human demonstrations give you one narrow band of trajectories and no exploration around failure. Thirty real demos is simply not enough: the pre-trained policy stalls, misaligns, and cannot recover.

VT-Refine (CoRL 2025, with NVIDIA Robotics) closes that gap by going real → sim → real.[5] The trick that makes it work is that this sensor is unusually easy to simulate. A piezoresistive array measures normal force at known grid positions, so a Kelvin–Voigt contact model — f_n = −(k_n·d + k_d·ḋ)·n, a spring-damper on penetration depth and velocity — reproduces the signal well enough to train on, and it runs GPU-parallel across thousands of environments. Compare that to rendering a gel deformation image per frame.

Step 1 / 4
Step 1 — Real 30 demos, collected in 30 minutes. Vision + touch, teleoperated. Enough to pre-train a diffusion policy that knows roughly what the task looks like — and not enough to do it reliably.
Real demos 30 episodes · 30 min vision + touch Pre-train diffusion policy imitation only GPU-parallel tactile simulation Kelvin–Voigt contact Large-scale RL fine-tuning sparse reward Deploy zero-shot to real
Figure 6. The real → sim → real loop. Real data supplies the prior; simulation supplies the local exploration that human demonstrations structurally cannot. Adding a new task means writing a sparse reward, not collecting hundreds more episodes.

The result is the strongest quantitative argument in this whole line of work, and it is worth reading carefully, because it says two things at once.

before RL fine-tuning after RL fine-tuning 40% 95% Visuo-Tactile 22% 65% Vision-Only Task success rate · bimanual assembly, asset 00186
Figure 7. Two readings, both true. (1) Simulation fine-tuning lifts both policies substantially — the sim-to-real gap is real but not disqualifying. (2) Touch changes the ceiling, not just the starting point: the visuo-tactile policy ends 30 points above the vision-only policy after identical fine-tuning. The gap widens with more training rather than washing out, which is the pattern you want to see if you believe the modality carries irreplaceable information.

7 · The research tree

Three questions, five branches, thirty works

Here is the whole map in one figure. The organizing principle is not the category taxonomy on the Awesome FlexiTac site — it is the story above. Three pillars are the questions asked in sequence; five branches are the directions the community took them; the roots are the prior work the sensor descends from; neighbors are independent groups building comparable sensors.

Hit Play the story to watch it assemble in narrative order, or click any node for what it contributed and what it inherited.

The map Every node is one entry in Awesome FlexiTac. Nodes with a dot were built on FlexiTac V1 or V2. Dashed nodes are context: lineage roots below, independent neighbours to the side.
Roots · dense tactile sensing before robot learning
The sensor
Three questions · first-author pillars
Five branches · where the community took it
Neighbours · independent, same sensing family
Click any node above for its contribution, venue, and links.
Figure 8. The FlexiTac research tree. Edges mean inheritance of an open problem, not citation. Two things the shape makes visible: the New bodies branch hangs directly off the sensor rather than off any of my papers — form-factor work only needs the hardware to be cheap and customizable — while Simulation is still the thinnest branch, with two followers. If you are looking for an under-served direction, that is where I would look.

Reading the branches

Fusion & representation is the most crowded branch, and it has moved from "does touch help" to "how do you route it." Policy Consensus composes separate per-modality diffusion policies rather than fusing features; ViTaS keeps one encoder but replaces alignment-then-concatenation with a soft-fusion contrastive objective; TacVLA pushes contact-aware tactile tokens into a VLA; FELT goes the other way and generates tactile signals from vision, which is an interesting attack on the data problem — if it works, you do not need the sensor at inference time. Object Pose treats touch as the observation for state estimation rather than control. Deform360 turns the whole thing into a dataset for deformable world models. TactX is the outlier: it attacks the representation itself, training resistive, magnetic and vision-based touch into one shared latent so a policy can cross sensors.

New bodies is the branch I did not predict. Once a tactile pad is a PCB file, people put it where they need it: an active palm that participates in dexterous manipulation (npj Robotics 2026), a force-controlled low-cost gripper, a fingertip-plus-palm in-hand system, and — least obviously — the feet and shins of quadrupeds for loco-manipulation. Two independent groups converged on tactile quadrupeds within a year.

Out of the lab is the two Analog Devices pieces. I include them not as papers but as market signal: a semiconductor company now ships a tactile part built on standard fab processes, claiming roughly 5× human-fingertip resolution. That is the strongest available evidence that this sensing family is not a research curiosity — and also a warning that the academic version has a limited window to matter.

8 · What this sensor is not good for

The honest limits

A frame that only lists strengths is a sales pitch. Piezoresistive arrays have real, structural limitations, and being precise about them is how you tell which of the branches above will hold up.

LimitationWhat it costs youUse instead
Normal force only No shear measurement, so no direct incipient-slip detection. You infer slip from pressure-pattern change over time, which is late. Optical (GelSight-class) or magnetic (ReSkin-class) skins
Drift and hysteresis Force-sensitive film is not a load cell. Absolute-force claims need per-pad calibration and re-zeroing; relative contact patterns are far more trustworthy. Load cells / F-T sensors for absolute force
Coarse spatial resolution ~3 mm² per taxel. Fine texture and surface geometry are below the sampling limit. Optical tactile for texture and fine geometry
Row–column crosstalk Multi-contact scenes on a shared grid can ghost. Matters more as arrays get larger. Per-taxel addressed arrays
So the honest positioning is: this sensor family wins on area, flexibility, cost, and simulation fidelity — which is exactly the combination you need for whole-hand, whole-body, and large-batch RL work. It loses on shear, absolute force, and fine texture. If your task hinges on detecting slip before it happens, use a different sensor. If it hinges on covering a lot of a robot in touch and training at scale, this is the right family.

9 · Seven open problems

Where I would work next

These are the gaps I see from inside the tree. They are numbered so they can be pointed at.

Fusion is unresolved

Geometric fusion needs calibration; attention-based fusion needs data. Nobody has shown one method that dominates across fixed-rig precision tasks and un-calibrated in-the-wild capture. A fair head-to-head on a shared benchmark does not exist.

Shear without a shear sensor

Can incipient slip be recovered from dense normal-pressure sequences alone, quickly enough to act on? If yes, most of the limitation table above softens.

Cross-sensor transfer — now contested

This was the flattest "nobody has tried" on the list, and TactX has since gone at it directly: paired contacts train resistive, magnetic and vision-based encoders into one shared latent, and a policy learned on one sensor runs zero-shot on physically different ones. That is the first real counter-example to "tactile has no equivalent of just resize the image." What remains open is whether it holds across geometries rather than modalities — a shared latent for two different pad layouts on two different fingers — and whether it survives a hardware revision, which is the case that decides if tactile data outlives the sensor that produced it.

The simulation branch is one paper deep

Kelvin–Voigt is a good first model, but no one has systematically characterised where it breaks — soft objects, rolling contact, adhesion, high-speed impact — or calibrated k_n, k_d from real data at scale.

Whole-body touch is barely started

The quadruped work is the leading edge and it is two papers. Large-area, many-thousand-taxel skins raise scaling questions — bandwidth, crosstalk, representation — that fingertip work never has to answer.

No tactile pre-training that people reuse

2,700 in-the-wild videos is a real dataset; it is not ImageNet. There is no released tactile encoder that other groups load by default the way they load CLIP. Until there is, every project pays the representation cost again.

Evaluation is not standardised

Success rate on a bespoke assembly task is not comparable across papers. The field needs shared contact-rich benchmarks with a mandated vision-only baseline — otherwise "touch helps" is unfalsifiable.

10 · Start in an afternoon

The actual on-ramp

The thesis of this whole post is that access changes what gets researched. So here is the shortest path from reading this to having tactile data on your own robot.

Step 1 · order
Send the PCB file out
Grab the flex-PCB design from the hardware repo and order it. < 1 week, ~$4/pad at small volume.
Step 2 · build
Assemble in ~3 minutes
Two flex layers, force-sensitive film, flat flex cable to the reading board. The fabrication guide is step-by-step.
Step 3 · read
Stream the array
32 × 16 reading board over an Arduino-class MCU. First heat-map on screen in the same sitting.
Step 4 · learn
Plug into LeRobot
LeFlexiTac wires the sensor into the LeRobot data and training stack, so you inherit the standard pipeline.

If you get stuck, the fabrication guide lists a contact address and the project has a Discord. The point of open-sourcing this was never the paper — it was to stop sourcing a sensor from being the part of the project that costs a semester.

11 · Browse the ecosystem

All 30 works, filterable

Below is the live Awesome FlexiTac gallery, embedded. Filter by category, click through to per-paper pages with abstracts and links. If you have a relevant work — whether or not it uses FlexiTac — open a PR and it goes on the list.

Awesome FlexiTac live gallery · 30 works
Open full site ↗
Scroll inside the window · Add your work

Cite this

@misc{huang2026flexitacmap,
  title  = {Making Touch Cheap: How One Open Tactile Sensor Grew a Research Tree},
  author = {Huang, Binghao},
  year   = {2026},
  note   = {Blog post},
  url    = {https://binghao-huang.github.io/blog/posts/2026-08-12-awesome-flexitac.html}
}

@article{huang2026flexitac,
  title   = {FlexiTac: An Open-Source, Scalable Tactile Solution for Robotic Systems},
  author  = {Huang, Binghao and Li, Yunzhu},
  journal = {arXiv preprint arXiv:2604.28156},
  year    = {2026}
}

References

  1. Sundaram, S., Kellnhofer, P., Li, Y., Zhu, J.-Y., Torralba, A., Matusik, W. “Learning the Signatures of the Human Grasp Using a Scalable Tactile Glove.” Nature, 2019.
  2. Huang, B., Li, Y. “FlexiTac: An Open-Source, Scalable Tactile Solution for Robotic Systems.” arXiv:2604.28156, 2026.
  3. Huang, B., Wang, Y., Yang, X., Luo, Y., Li, Y. “3D-ViTac: Learning Fine-Grained Manipulation with Visuo-Tactile Sensing.” CoRL, 2024.
  4. Zhu, X., Huang, B., Li, Y. “Touch in the Wild: Learning Fine-Grained Manipulation with a Portable Visuo-Tactile Gripper.” NeurIPS, 2025. arXiv. Best Demo Award, RSS 2025 Workshop on Robot Hardware-Aware Intelligence.
  5. Huang, B., Xu, J., Akinola, I., Yang, W., Sundaralingam, B., O'Flaherty, R., Fox, D., Wang, X., Mousavian, A., Chao, Y.-W., Li, Y. “VT-Refine: Learning Bimanual Assembly with Visuo-Tactile Feedback via Simulation Fine-Tuning.” CoRL, 2025. Best Paper Award, IROS 2025 AHFR Workshop.
  6. Full reference list with links for all 30 works: Awesome FlexiTac.

← All posts · Related: a full survey of tactile sensing, 2020–2026 · Home