Are you experimenting with small networks or building large, multi-block architectures?

This helps optimize UI performance and features.

If your day-to-day work is deep in PyTorch and you re willing to break early builds, I want to hear from you.

Leave a comment and I ll reach out.

Planned:

Drag-and-drop layer editing

Reusable blocks (ResNet-style)

Automatic shape tracking

Even experienced users hit snags with shape mismatches and repetitive boilerplate.

Where does it break down for you?

Do you sketch models, copy older projects, or code directly in VS Code?

Understanding your workflow helps me design better drag-and-drop components.

NetSmith is PyTorch-first.

If you could add one feature tomorrow for PyTorch models, what would it be?

NetSmith currently exports clean PyTorch modules.

I can expand the export options what would you prefer?

• Standard nn.Module

• Lightning-style modules

• Scriptable modules

• Custom template support

When you re wiring up a new architecture in PyTorch, what slows you down the most?

Layer selection? Shape debugging? Boilerplate? Something else?