Might be easy...might not be. It depends the code they already have in place. I'm sure your husband knows what I mean if he's ever had to support some horrible code written by someone else! Sometimes it's easier to rewrite an entire program rather than try to modify some of the junk some other people write. Cost of implementing any changes also depends on how "robust" (read "bullet proof!") and well tested the company wants the change to be. I've found smaller companies tend to be more willing to make changes to their software quickly than larger companies that may have hundreds of thousands or even millions of daily users that will be impacted by any changes. (I once saw a fix that I could have implemented in less than 5 minutes take over a week to go through channels and be evaluated and implemented. It boggles the mind, but that's how paranoid some companies can be about the potential for introducing a buggy change.)
Bottom line is that "if" they've written the existing code well it might be an easy change...but even if that's the case it might cost more money/resources than they are willing to commit to the work due to their release protocols and the work they already have on their plates.
Personally...I'd like to see them implement an option for offline recipe support, I'm just aware that it might not be something to expect any time soon.