KE5ZQV field note · 5 min read

Building Log2Go around real NetLogger use

Why the project exists: replacing awkward mobile net workflows with a clean app that understands active nets, rosters, AIM/chat, and normal logbook needs.

Why Log2Go exists

Log2Go is being built around real operating habits, not just a blank form with a callsign field. A lot of my radio activity is tied to nets, mobile operation, and keeping usable records without being stuck at a desk.

The idea is simple: make logging practical from the phone first, then grow toward a cross-platform ham logging system that also works on desktop.

What NetLogger taught us

NetLogger-style net operation shows what hams actually need during a net: active net lists, rosters, check-in status, AIM/chat, net-control context, and a way to log contacts from people already on the roster. Those are not side features for a net operator; they are the operating surface.

At the same time, mobile operation exposes the friction. A phone needs a cleaner flow, larger touch targets, fewer assumptions about being at a desk, and better handling for station profiles and location.

The Log2Go direction

The early goal is mobile-first logging that works for general QSOs, mobile and portable contacts, contest/special-event style contacts, and net contacts. The longer-term goal is bigger: Android first, then iOS, then desktop clients, all tied together by a backend that can sync, export, and eventually host net operations directly.

For nets like N0SWR, the long-term hope is to support a modern hosted net service: roster handling, check-ins, AIM/chat-style messages, and logging designed around how net users actually operate.

Design rules I care about

• Local logging should work even when the network does not.
• Net mode should respect volunteer-run services and avoid abusive polling.
• Station profiles should preserve operating context.
• ADIF export should remain available so users are not locked in.
• Online integrations should be clear about what uploaded, imported, or confirmed.
• The app should be useful to everyday hams, not just software people.

Credit and independence note

NetLogger is credited to its respective authors and rights holders. NetLogger 3.x is copyright © 2015-2018 John Marvin, AC0ZG; NetLogger 2.4 is copyright © 2001-2009 N1HWQ. Log2Go is an independent project and is not affiliated with or endorsed by NetLogger.org or the NetLogger authors.

Bottom line

Log2Go is not just a clone of an old workflow. It is a chance to build a cleaner logging and net-operation system from the way we actually operate today: mobile, connected, net-aware, and still respectful of the ham-radio services that got us here.

This article is general ham-radio operating and station-building information, not legal, safety, or manufacturer-specific advice. Verify regulations, manuals, ratings, and measurements before acting.