brainstorm list: UI/module overhaul to 3.x? merge with EMF?

I normally don't this, but as I am currently using your module I come across quite a few ideas/additions/suggesting that I rather share for you to consider and others to comment on, rather than keeping them for myself. Please don't take this any other way that throwing out ideas, or wishes for the future of a robust yet flexible integration with mailchimp because their API is quite strong. Although I am tempted to contribute to this module in a more active manner (depending of you willing to accept that or not) I am currently lacking the time for it.

So far I can think of quite a few things, if any of this things needs its own discussion we can always create issues form them.

* Merge with EMF.

I think both modules does very good things on its own. I liked the idea of a framework so I chose to use that one first. After a little few tests, I felt it a little uneasy in terms of user UI (specially concerned about the user UI). I also contributed a small patch to it which took a little while from the maintainer to give feedback on it (which is normal). I then switched to this module which, IMO, had a better UI around the mailing lists for the normal user and a few more options to play around with (double opt-in, etc.). One thing I liked about EMF though, is the administration UI, although not entirely user-friendly, it was clear and extendable and with room to add more options.

So one thing that might be great happening is to join efforts between both module's developers and contributors and maybe work towards a new release of either module (I'd suggest emf as it's goal to be a common framework is a nice one).

Either way, a few of my ideas:

- Admin overhaul: There seems to be some more options we can use from mailchimp fields, like required field, show field, order, etc. which might be nice if those gets sync'ed and administered by the administration of the site. I know you mentioned that the settings page is already very busy so one idea (taken from emf) might be to hold the list information in an own database and have a list of lists, and also a list of fields, and those things manageable on its own.

- Use the Mailchimp API more cautiously. The API is used all over the module, which is not a bad thing at all, but I wonder if any error or communication problem exists between the site and mailchimp it may slow or affect the site. I wonder if it's better to sync the mailchimp on a timely basis (and eventually manually if needed) and then use only local stored information within the module? (also an approach that seems to be happening on EMF).

Well, so far this is what I have in my mind, let me know your thoughts.

a.=