YUDU & Development Processes

We’re often asked about how our development process works here at YUDU, by both clients and potential clients, so I feel it would be useful to give a very brief overview of how our development process works and what elements constitute it, as it fits fairly neatly into our overall ethos as a company, namely simplicity and putting the client first.

Most of the “grunt work” of any development involves working on aspects that don’t really visually show up on the client’s end, but can tangibly be experienced through improved performance. These usually involve things like the day-to-day business of fixing bugs, making the software itself more robust and secure, more consistent, as well as the less common development work to support infrastructural improvements to the system, like moving datacentres. Alongside this, we employ our in-house developers to work on more aesthetic elements of the software, like making the various UIs of our platforms more intuitive, and we’ll have more to report on this front later on in August.

Another major part of our development process is taken up by feature or enhancement updates. We aim to deliver three to four major feature/enhancement updates a year, things such as our categories feature, or entirely new products with cross-platform functionality, greater subscriber management options among numerous other things. We adopt a largely democratic approach to what we prioritize in this field of development, and as a result we encourage feedback on what our clients would like to see. Once we feel we’ve gathered enough data, our management team and developers will meet to discuss which prospective features are receiving the most requests, and prioritize those accordingly (within reason of course). Alongside this, we also have a strong History of solid custom-development work in partnership with some of our major clients; essentially, if a client wants a very specific feature or enhancement, we can sit down with them and discuss the feasibility, funding and time-frame involved in developing it and naturally, these sorts of projects will involve constant consultation and view on work done so far with the client. We’ll also have more to report on this aspect of the process in August.

Ultimately, we’re committed to long-term and continuing investment in our software’s development, as we see our platform as non-static, something that is continuously evolving and improving, be it through performance, better automation or greater feature-richness. We want to ensure that whoever purchases our platform can come back a year later and always notice a few new aspects of our system they can play around with. Essentially, we see YUDU PRO customers, of any stripe, as buying into a package that includes future development work.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s