@Jay I do my part with the spam when I visit but I’m not here regularly. It does seem worse.
To be totally blunt: If a user can’t get over a little extra friction when signing up for the forum, they’re not going to be Legend users for long, anyway. Between the learning curve and the bugs, this app basically demands that users are a bit more patient than usual. It’s absolutely worth it, of course. This thread itself is all the proof you need for that.
@LauraH, you already know my experience is basically identical to yours. There are a number of core things Legend does that absolutely nothing else can do – or can even be shoehorned into approximating.
Answering your question: it’s about the same as it was. During the recent rough patch I stopped using beta entirely because I just needed to get my work done and didn’t have the time to faff with all the setbacks. It sounds like that is over now…but I still haven’t switched back. Too much to get done. I haven’t actually lost any data yet, though. I’ve lost work that needed to be re-created but not (I don’t think) any content.
Only once in 6 years have I been entirely locked out of access to my Legend docs, and that happened this summer. Jay took care of me right away of course, but there’s no getting around that risk. I absolutely do not rely on Legend for time-sensitive info: I use Apple’s calendar / reminders apps to schedule things that actually can’t be missed. Of course I would LOVE to have everything in Legend so I don’t have to double-enter critical events (and risk mistakes in keeping the duplicate entries current). But I haven’t gotten a reliable notification from Legend since the day I started using it.
Luckily (for me), the nature of my work is less about deadlines and appointments. It’s more like task-sequencing. I basically work for myself so if I don’t get something done today…well I just keep working on it tomorrow until it does get done. Ultimately I can’t start the next thing until the current one is done – when it’s “due” is immaterial. So I have dates in my main project task list. Legend lets me understand the common traits of tasks in my project across multiple unrelated subject areas, then put them into a serial list that optimizes my time, protects against mistakes, and reduces wasted material. This is irreplaceable.
So for me, an unreliable Legend that needs occasional repair and rework is better than none at all. Even if I had to spend a couple hours a week on Legend cleanup, it would still save me so much time and risk in my current project that it’s the lesser of the two evils. Yeah, it gets really frustrating…but there is no alternative. Obviously it’d be great if it weren’t that way – and once this huge project is over I plan to do my part to help that happen – but for now I have just learned how to proceed cautiously. I compartmentalize my work where possible for easier damage control, avoid features that have proven to be landmines, and have gotten comfortable with restoring from backups.
