Not sure this is the proper channel to this suggestion, but...
Podio, alongside Automattic and Google, is one of the companies that had more impact in my and my company philosophy and mindset and I always praise all the 3 (like in here, Google Translated from portuguese http://j.mp/R2JpLr ). So, it's natural to interlink ideas from each other and now it's time to give a suggestion to the Podio team.
As the development of Wordpress core is open and made by a community of developers, they made the issue tracker open and, therefore, the plugin and themes developers know what is coming far ahead of the release date and are able to prepare changes to their codes and architectures prior to the release, avoiding bugs and and other headaches, while allowing to more people testing and bug hunting.
I know Podio is not an open source / community project, but I think would be great to Podio and the Podio users community having this kind of approach too in the last phases of the release cycle, allowing the app builders and API users to prepare themselves and their solutions (like Zappier), also allowing workspace managers to test, bug hunt and, specially, to prepare different workflows and update training assets (like tutoriais and docs) for non-tech users of the workspaces.
A real example from my company: we create content for several clients and we have in-house copywriters, freelance copywriters and, in some cases, client copywriters with different levels of experience with web and specially Podio. So, we created some training material - both in documents and videos - showing the steps AND screenshots of from Podio apps. Yesterday, a new and gorgeous interface was revealed and while sure it's more clever and slick, I was taken by surprise and have to create new materials. No big deal, really, but it would be great to have done this prior to release and prepare (or, to be honest, to tease) my team for these great and wonderful changes.
I know it reads a little bit egocentrical, but is not.
Please sign in to leave a comment.