The MLS system landscape and the MLS Vendor of the future.

Good stuff Greg. I disagree with one point though – “With the recent acquisition of Tarasoft by CoreLogic lowered the choices in MLS systems options available.” – that move lowered the number of MLS *vendors*, but not the number of MLS systems.

Matrix gives Corelogic yet another non-Flash option to offer to work on iPad. – Corelogic also has been able to offer non-Flash Innovia and Innovia mobile.

We’ve been talking about focus and integrations for years now – I still think we’re heading that direction as well – but it’s not going to be all that successful without data standards. I’m still hoping that RESO can achieve some momentum and develop data standards for moving contacts and saved searches, which together with some preferences yields “prospects”. Add a bit more and you have the client “activity” RETS payload being discussed. Being able to move and synch that data could lead to easier system transitions and the ability to have third party products handle the client-collaboration elements of MLS entirely (or provide a better mobile interface to it) rather than locking people into a single tool using their data as handcuffs. There are so many other areas where data standards are needed but I’ll leave it at that.

Good stuff. Especially the warning of not “putting all your eggs in one basket”. Man,that would have one ugly ending!
But I’m not seeing the opportunity for 3rd parties you speak of. For instance, CoreLogic now offers Realist for free and nearly free (depending on which Association they are pitching). The more they offer for free, the less competition there will be.
The only 3rd party opp I see, I guess in this situation, would be if a current Realist paying Association called out Realist for offering that product for free when they and others are still paying full price.

Good article Greg. We were going through this same debate a while go (How to make our system Cross Browser compatible) and almost came to the solution of using Flex (Flash) or Silverlight. Our final decision was of course to go with standard HTML and Java Script and good thing we did. In the course of development we were excited when it naturally started working on iOS and Android devices, although another problem presented itself which is the interaction a user has using a mouse and keyboard is completely different than an interaction with a multi-touch interface. So even though we went with web standards and it does work on mobile devices, we still may in fact look at app development specifically for mobile to accommodate the needed difference in interface.

As for the ‘Flash is Dead’ topic; I have a coworker that I debate this with occasionally. He is a pure Apple Fanboy and so he of course wants Flash (and all middleware) to die a quick death. I’m however on the other side of the fence. I understand the argument “that it gets in the way”, however I still see the need for it. Browsers are starting to get more friendly and “standards” based, however I don’t believe it will ever be perfect. Even with HTML5, the browser controls the rendering and thus every browser will have it’s own “quirks”. The only real way to control the user experience and make that experience consistent across all devices is with a consistent software on each said device. Be it Java, Flash/Flex, Silverlight, etc. it takes that control away from the browser so that developers don’t have to spin their wheels tracking inconsistencies across numerous platform/browser combinations.

Also like Robert said about iMapp, Hawaii Information’s own REsearch program also has fully integrated Public Records and Parcel Based Mapping into our MLS system for the past 20 years. So its fun seeing everyone jump into the parcel based MLS arena like they were the first. ;o)

Now I’m in an interesting position being that Hawaii Information is both a “Vendor” and an “MLS”, and though it goes against the grain I’ve been told I should believe in, I believe full-hearted that the MLS industry is in need of a business model change. If I were to form my perfect vision of the future it would be something like this. Each area would still have an ‘MLS’ which would control the rules and regulations, provide agent training and member services, manage local rosters, and handle the data aggregation. This data would then be placed into a standards (RESO?) based database which Vendors would the be able to tie their system into for a per-member price to the MLS. Upon the contract being signed, that MLS’s members then have the ability to subscribe for a monthly fee to the Vendor. This would put all vendors on equal footing as the multi-year contracts go out the window and it no longer is about ‘Who you know’ and more about how good your system really is. This would also greatly increase the competition, which has proven many times over to benefit the members with options, lower costs, and increased support. And finally it would also help the 3rd parties as they no longer would have a million hoops to jump through. I also fully agree with Greg that the future MLS system will be more open to plug and play API style complete with a “app store”-esque purchase mechanism. 3rd party software could then be included as additional options “Would you like fries with that? How about upgrade to CloudCMA for an additional $9.99?”.

Okay its Friday and I need to stop day dreaming. Have a great weekend everyone and Mele Kalikimaka me ka Hau’oli Makahiki Hou!