Using a Smartphone as a Macro Keypad for AutoCAD - Another Take on Workflow Customization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
AutoCAD already offers a rich set of customization tools - the CUI editor, tool palettes, command aliases, and AutoLISP routines - and over the years I've explored most of them. This post is about adding one more layer to that stack: turning a smartphone into a dedicated macro keypad for AutoCAD, without purchasing any new hardware.
Background
A while back I used a 3D mouse with programmable buttons, and it noticeably improved the fluency of my CAD sessions. When my workflow shifted away from 3D modeling I sold it, but the memory of having key commands literally under my fingertips stuck with me. As my CAD workload grew again recently, I started looking for a cost-effective way to recreate that experience.
Why a Phone Instead of a Physical Macro Pad
A dedicated external macro keypad is the obvious solution - one button per command, no hunting the keyboard. But it means buying hardware and finding space on the desk. Then it occurred to me: I already carry a touchscreen device every day. Why not use it?
After some research I found a category of apps originally designed for PC gaming remote control that do exactly this - they turn a mobile device into a fully customizable button controller communicating with your PC over Bluetooth or Wi-Fi. For CAD use, that translates into a programmable softkey panel you can design yourself.
My Layout
After a few days of iteration I settled on a layout I keep next to my laptop under my left hand:
- Top row: Most-used native AutoCAD commands (LINE, TRIM, OFFSET, etc.)
- Middle two rows: Custom AutoLISP-based commands specific to my surveying and documentation workflows
- Bottom area: A touchpad strip with modifier and function keys
The result is that nearly every command I reach for during active drafting is accessible with a minimal hand movement - less mouse travel, fewer keyboard combinations to remember. You can also create multiple "pages" of buttons, so maintaining separate layouts for AutoCAD, Civil 3D, or other tools in your stack is straightforward.
Real-World Performance
Ergonomically, the phone sits naturally under my left hand and doesn't displace the keyboard or mouse. The compactness of the touch panel means I rarely lift my hand off the surface.
A few limitations are worth being honest about:
- Sending Enter cleanly after typing a numeric value in the command line still requires some workaround in my setup
- A stable connection worked best over Bluetooth in my tests; Wi-Fi and USB were less reliable depending on the app
- Touch accuracy on small buttons takes a day or two to get used to
Despite these, the workflow improvement was meaningful enough that this has become a permanent part of my daily setup. I'd estimate roughly a 10% gain in command-entry speed on a typical drafting day.
The App
The tool I used for this experiment is Monect PC Remote, a free-to-try app available for Android and iOS. It's not CAD-specific, but it's flexible enough to map virtually any keystroke or command string to a button.
A Thought for Autodesk
This whole experiment made me wonder: would there be value in Autodesk releasing an official AutoCAD Companion app for smartphones and tablets? Not a mobile viewer - AutoCAD web and mobile already cover that - but something purpose-built for remote command control and CUI customization from a handheld device. An official app could go much further than a generic gaming remote: it could read your existing CUI profiles, sync tool palettes, suggest frequently used commands based on your session history, and maintain a secure connection to the desktop client natively. Given how many AutoCAD users work on laptops at client sites or on-site visits, a polished first-party solution like this could be a genuinely useful addition to the ecosystem.
Has anyone else experimented with phone-based macro layouts or similar setups? Would be curious to hear what tools and configurations the community is using.
The original version of the article in Italian is available at the following link