Design roles are merging, and the tech stack is exploding.
Whilst prepping for my first venture sprint next week, I audited every design tool that's delivered value over the last two months.
Here's what I'm noticing:
→ Figma & Claude are my power duo. Work begins in Figjam, then Claude synthesises insights and requirements into structured JSON files that I use to prompt Figma Make for rapid prototyping. Claude also helps me generate design system documentation and prototype code for complex interactions back in Figma.
→ Specialised tools add value but bleed my budget. Mobbin for product discovery, Midjourney for brand exploration, Lottie for animation - each solves a specific need, but at $20/month each, it's unsustainable. Will these eventually consolidate?
→ Freemium resources are keeping me afloat. Design Systems Index, Cosmos, and Untitled UI are lifesavers to get inspired, but how long before they're behind paywalls too?
It's easy to get lost in a sea of surface-level applications. For the solo designers out there, it feels like our job isn't mastering 30 tools - it's designing an affordable workflow that delivers value with 5.
What's your strategy - consolidating or expanding?
Navisworks can now create Autodesk Data Exchanges!
That’s a big step forward for interoperability.
Data Exchanges use a neutral format that works across any application with a connector, including:
Autodesk tools - Revit, Inventor, Civil3D, Navisworks, AutoCAD and Dynamo
Other design tools - Rhino, Grasshopper, SolidWorks and Tekla
Business applications - Power Automate and Power BI
Once created, an exchange can be shared between these applications without needing to convert files.
What’s New:
You can now create Data Exchanges directly from Navisworks Manage.
💡That means any format supported by Navisworks can now feed into other connected tools.
Here I took advantage of another recently released feature: the scan to mesh workflow using ReCap Pro.
ReCap → Navisworks → PowerBI
This allows point clouds to be converted to segmented meshes, and exported as native Navisworks and Revit files.
In PowerBI I can now dashboard all design components across a project, not just Revit files.
Think Point Clouds, SketchUp, MicroStation and more.
Check out what applications are on the data exchange roadmap and submit your ideas here:
https://lnkd.in/g3TykV9f
For more check out my previous post on running clash detection on scans in ACC:
https://lnkd.in/g85jsTUY
See the Data Exchange help page to join the Beta and get set up:
https://lnkd.in/gestwGX4#Autodesk#RealityCapture#Revit#PowerBI
LLMs are beginning to serve as intelligent copilots directly inside your favourite 3D design applications!
Using Claude desktop paired with local MCP (Model Context Protocol) servers, you can build AI-powered assistants that seamlessly connect Claude's intelligence to your design tools. MCP acts as a universal connector, enabling Claude to access your software's data and functionality.
🔧 Integration is surprisingly straightforward—simply edit your Claude desktop config with the matching JSON file for your software of choice. The ecosystem is growing rapidly!
I've created detailed tutorials to help you get started:
1️⃣ Rhino MCP setup: https://lnkd.in/essXWjsp
2️⃣ Blender MCP implementation: https://lnkd.in/ecSuJfEv
Additional MCP GitHub repositories to try out:
Unreal Engine: https://lnkd.in/eQvQN6g5
Revit: https://lnkd.in/eVExrUEp
ComfyUI: https://lnkd.in/eCyedQea
Blender: https://lnkd.in/edbB8rvZ
Rhino/Grasshopper: https://lnkd.in/eJvd_kyw
💡 While my testing with Rhino, Grasshopper, and Blender shows we're not yet at full practicality, the progress is undeniably exciting! Looking forward to exploring the Unreal Engine and ComfyUI MCPs next.
Instagram: https://lnkd.in/enjnZ5ep
Youtube: https://lnkd.in/e3rnrAPU
I watched a designer turn a 12-page PRD into a user flow in 43 seconds.
Not a sketch. Not a rough draft. An editable, team-ready flowchart in FigJam.
The Claude + FigmaJam integration launched last month, and it's changing how product teams work.
Here's what I'm seeing:
→ Teams creating diagrams earlier in the process — not after decisions are made, but as a way to make them
→ Designers with zero coding background turning flowcharts into working HTML prototypes in under 5 minutes
→ PMs catching edge cases in sprint planning that used to surface in QA three weeks later
Three workflows worth trying this week:
1. PRD to user flows
Upload your requirements doc. Get an editable flow diagram. Your team reviews it before standup ends.
2. Flowcharts to working code
Draw logic in FigJam. Claude Code reads it and builds a functional prototype. Designer Felix Lee calls this "vibe coding."
3. Screenshots to prototypes
Screenshot any UI. Get a clickable HTML version. Test five navigation patterns in an afternoon.
The shift isn't faster diagrams.
It's collapsing the time between understanding a problem and visualizing it with your team.
Setup takes 2 minutes: Claude → Settings → Connectors → Figma.
What's your biggest friction point right now — alignment between specs and flows, or getting testable prototypes without engineering time?
#ai#product#productdesign#ux#design
💡Bridging the designer-developer gap: challenges, solutions & tools
Disconnection between design and development is a prevalent (and severe) problem in product design. In today's workflow, designers hand off design files to developers to wait and see how implementation turns out. Misinterpretations of design specs, constant back-and-forth, and tech feasibility issues can easily turn the handoff into a prolonged and frustrating ordeal.
Here are some strategies to help bridge this gap:
✔ Early and continuous collaboration. Engage developers in the design phase to provide feedback on feasibility and technical constraints. It will help prevent designers from crafting something that cannot be built or is too expensive/complex.
✔ Using MVP test implementations: Minimum Viable Product implementation can convey design intentions more effectively than static mocks. MVPs are especially useful for communicating dynamic elements, such as animated transitions between system states.
✔ Design system and versioning: Version control systems help to track changes in project files, manage iterations, and ensure consistency.
✔ Cross-training: Designers should learn basic coding principles and developers should learn design fundamentals.
However, despite these strategies can boost product development efficiency, they still feel like treating symptoms instead of the cause. There is one fundamental problem in product design that leads to the gap between design and development—different environments in which designers and developers operate. Designers use tools like Figma to create detailed designs, while developers use IDEs like Visual Studio Code or IntelliJ to write and manage code. After the handoff, developers need to manually recreate designs from Figma files in the source code. This translation is time-consuming and prone to errors. Details like exact spacing, colors, font style, and component behaviors can be misinterpreted.
Why should design and code be separated in the first place?
The best handoff is no handoff. Having a single tool for both design and development will reinforce the product creation process, and Codux (https://codux.hopp.to/nick) is a nice example of such a tool. It's a collaborative development environment for designers & developers that allows crafting UI design using a visual editor. Every change you make visually reflects in the clean and human-readable code (and vice versa). Because the boundaries between the roles of UI designers and front-end developers have already started to blur, tools like Codux represent the future of front-end design because they take the best things from both design & development worlds and offer complete control over the design solution. And that's what will help us solve the fundamental problem of the product creation process—design handoff. We simply won't need to have a handoff as a separate step because handoff will happen all the time.
🖼 Design pong by Ahmed Sulaiman#UX#design#productdesign
Integrating Autodesk and Esri softwares can revolutionize how we approach urban planning, construction, and infrastructure management.
Here’s how to create a comprehensive solution!
Understand the Power of Integration:
Autodesk excels in Building Information Modeling (BIM) while Esri is unparalleled in Geographic Information Systems (GIS). Combining these strengths creates a seamless workflow that bridges design, construction, and operational phases with geospatial intelligence.
Use Common Data Environment:
Leverage a common data environment (CDE) to facilitate data sharing. Autodesk's BIM 360 (Construction Cloud) and Esri’s ArcGIS Online can act as central repositories, ensuring all stakeholders access up-to-date information.
Employ Interoperability Tools:
Utilize tools like Autodesk Connector for ArcGIS, which enables direct data exchange between Autodesk Civil 3D and Esri's ArcGIS. This integration allows the import of GIS data into Civil 3D and vice versa, maintaining data accuracy and consistency.
Optimize Workflows:
Integrate workflows by using Esri’s ArcGIS Pro to perform spatial analysis and visualize BIM models in a geospatial context. Autodesk Revit and InfraWorks can then refine these models, incorporating precise geospatial data for more informed design decisions.
Enable Real-time Collaboration:
Foster real-time collaboration through cloud-based platforms. Autodesk Construction Cloud and Esri’s ArcGIS Online enable teams to collaborate on projects, update data, and share insights, enhancing productivity and decision-making.
Enhance Project Outcomes:
By integrating these powerful tools, you can achieve better project outcomes. Enhanced data visualization, improved accuracy in design and planning, and streamlined workflows lead to more efficient project delivery and sustainable infrastructure development.
Integrating Autodesk and Esri is not just a technological advancement; it’s a strategic move towards smarter, more efficient project management. Embrace this integration to unlock the full potential of your projects.
#Autodesk#Esri#BIM#GIS#Integration#UrbanPlanning#Construction#Infrastructure#Innovation