I can't understand the level of frustration here - I am using my SS daily - it is rarely unplugged.
When I mention it to people I tell them it is complex. more so than most devices - but that with that goes great flexibility and depth. They will need to 'play around' with it more than most footpedals, but it will give back so much more in return. . Memory footprint is not an issue imo, anyone doing music should have at least 8 to 12G ram anyway; startup time in hosted is pretty irrellevant also imo, but i have computed since the 70's so I know s--l--o--w-- . . . Plus I guess I know what it is doing in that time - quite elegant copy-protection stuff . . .
You should have noticed in other posts since May that v1.2 is indeed nearly here - having seen an earlier beta, I know there are some good improvements on the way for those having problems at the moment including a 'simple editor' for people wanting easy basic control, saving hosted to standalone, librarian etc And yes -debugging can take time but many devices never get upgraded - this is a very modern phenomena. Very few of the products I have ever bought have had as much access and feedback and updating as the SS has had. My Roland VG99 is unlikely to ever get upgraded or my FC300 foot pedal despite many requests.
Re; alternate app development - many messaging protocols of many manufacturers are never released and their is no real reason why they should be if they are proprietary - ie Rolands RRC2 protocol, so I will consider myself very fortunate if they release such low-level info. I could, but am not bothered to, have a sniff and a hack to extract the necessary info but prefer to wait for KMI to finalise their end first. I have already had a play at using the raw MIDI output into Max, Processing, SC, QC etc and had a bit of a behind the scenes look at SS app. Sure the lack of return messaging was an issue but I used the computer for that. I guess if you wanted you could always start developing your app now and plug the other bits(messaging etc) in later when available. I've done a bit of dev myself, just not a great deal in objectiveC. I also know a substantial amount of programming and Max dev by many talented people went into producing this app . . .
So anyway, remember this is a 'USER' forum - not actually a direct line of contact with KMI, although they do drop in regularly - so particular requests etc should be sent to KMI directly, not just posted here.
In closing I find the whole package quite inspiring and am spending lots of time integrating it into my various systems and pursuits - solving most problems or accepting current limitations and sending off a future feature request straight to KMI with good feedback. I sympathise with those who are experiencing difficulty . . .
Hope that v1.2 will assuage some of your concerns . . .
I'm lovin' it . . . .
KMI StringPort_1650, SoftStep_VK2 v1.2 & MIDI Expander; Mac_Moore Guitar,
Roland VG 8, 88 & 99, YamahaVL 70m; OSX 10.6.8, iMac i7 2.8G QC; MaxMSP 5.1.8, Ableton Live 8.2.2, M4L, SC3, QC, cSound, etc, etc,