Module Update Differences Report

The tool has existed in it’s current state for a few months and works really well. I built a DataSource to alert me whenever the number of updates available changes, which prompts me to refresh the report. Unreleased as of yet, given it’s proprietary IP. One of two things could happen:

1. LM builds these features into their module toolbox. I’ve already had several promising conversations with @Michael Rodrigues about it and I’m enthusiastic about his plans. We spoke about several of the key features that I built into my tool and how they could be built into the module toolbox and why they needed to be there. We also spoke about some features that I didn’t build in, but that I wanted to and he already had identified the possibility, but had yet to have anyone voice the value/use case.
2. LM delays building these features into the module toolbox, making the module toolbox a veritable earwax flavored jelly bean. In that case, I may offer the update report as a service to other LM customers. I’d have to determine the demand and whether or not it would be something that would be financially profitable for us. The idea would be to have you give me the API credentials to your portal, permissions limiting me to just the modules, and I’d run the report on a regular basis and host it on a password protected space where you’d access it. DM me if you’d be interested. I have no idea on cost nor price.