User name:
Password:

Forgot password? - Sign up

229443365 AA0HC AC2OK ajoyraman BG5ARO BG7KAN BG8TFI BG9JPH billesch chapner Codeman26 cordobes dingrui DL1WWE DL8CQ DM6MT dorkoski driver4867 drkarthik7 ea4acz edwardgodlevsky gmmotorhead I2OHT icio imachita IU6UAM JanuszK jwetzell km7goo lengowong m1919 M1MRB maplesloth Mujue n3ocl N9OJR nhatthp Nirodha NT4T OK1VAV oz8sw PA3VJ ph9hb PY1LU Quartich Raposinho sam6game Slater solamnia SP3WAM SteppinOut TchorT test UR3WEW UR5SMS vk2rh xjluojp zerobuttons ZS5HUX

73 all,

I'm a relatively new face here, still working on my own copy speed. Over the last several months I've been building a mobile app called
MorseKit (iOS + Android) that tries to take some of the ideas I learned about from this community — Koch progression, audio-first
recognition, weak-character review — and put them in a phone-shaped tool you can use away from the rig.

I want to be upfront: this is not meant to replace LCWO or any serious desk trainer. LCWO is what you use when you're sitting down to study.
This is what you reach for at a bus stop, in line at the grocery store, or before bed when you can't fire up the computer. Different context,
different tool.

What's inside:
- Koch-style lesson progression across 12 "bands" (alphabet → digits → punctuation → Q-codes → prosigns → noisy-channel decoding → speed →
operator phrases)
- SM-2 spaced repetition on the characters your ear keeps missing
- Real-time WAV tone synthesis (no canned clips), 5–20 WPM, 550–750 Hz
- A decode terminal for free-form Morse ↔ text with playback
- Three short practice modes: 60-second speed round, letter drill, word blitz

What I'd genuinely like from this group:

1. Pedagogy critique. I made tradeoffs. I'd rather hear what's wrong from operators who've actually trained their ear than from app store
reviewers who've never sent a CQ. Where am I cutting corners that matter?
2. Timing & pitch. Default is Farnsworth-ish at lower speeds, character speed at higher. 600 Hz baseline. Open to being told this is wrong.
3. What's missing. Head copy drills? QSO simulator? Specific call-sign drilling? Tell me what a serious learner actually needs that the app
doesn't have.
4. Where it breaks for licensed ops. I assume some of you will install it for 10 minutes and immediately spot something amateurish. That's
the feedback I want most.

I'm not asking anyone to review it on a store or share it. I just want the technical critique from people who know more than I do, so the
next version is sharper.

Links if you'd like to take a look:
- Android (Google Play): https://play.google.com/store/apps/details?id=app.morsekit.morse.code.translator.cw.trainer
- iOS (App Store): https://apps.apple.com/us/app/morsekit-morse-code-trainer/id6761839923

73 and thanks in advance for the honesty,

cwdev73

Heya,

Couple of immediate things from me; the first is that the app pushes you straight into transmitting. I think a lot of people (or at least me!) would like an option just to use it for listening practise.

Secondly, the send-mode appears to be straight key only. Lots of people out there (or maybe just me) don't want to/never plan to use anything other than a paddle.

I think forcing a send mode is okay and whilst I'd prefer a listen-only mode I'd probably get over it, but the requirement for straight-key sending would likely be enough to push me entirely away from the app.

Also seems the wpm limit is 20; which is pretty low. I know some programmes like CWOps get people to learn at say 25wpm but 6wpm effective or even 30wpm with 6wpm effective. That's what I'm using so the limit felt pretty low for me. I prefer a higher wpm because it prevents me counting the dits/dahs but the lower effective helps beginners.

Just some thoughts, app looks good so far!

de 2E0IKA

Hi 2E0IKA, thank you so much for such a detailed and technical critique; this is exactly the kind of feedback I need to sharpen the app. I’ve taken your points to heart, especially regarding the need for a dedicated listen only mode, adding paddle/iambic support for those who don't use a straight key, and raising the 20 WPM limit to better support high-speed character recognition. These improvements are now at the top of my roadmap to ensure MorseKit serves serious learners and licensed ops more effectively. Thanks for the honesty and helping me improve the tool.

73

Heya,

This is great news; let me know when you've made the changes and I'll do a deeper dive. I could definitely give you a bunch of feature requests for things I've struggled to find elsewhere.

I'm still relatively new to CW myself, but I'm comfortable at 12 wpm and mainly here for SOTA/POTA activations

Looking forward to how things develop!

73