Merging of UI strategies

Haven’t written to the blog for a while (just posting links to the facebook page) – reason is the best worst: work 🙂 But indeed, this is a good kind of work. Recently, as part of a streamlining step, my team was repointed to work inside a larger organization – namely Client Platform Engineering. So, what does such a merge allows us – me – to do? What is (a) Client Platform, indeed?

Let’s dream big (I like doing that – dreaming of platforms and architectures generally makes you happy). You are developing applications for clients. You are developing a platform for building such said applications. You make it easy to comprehend but hard to cope, trying to cover all flavors – from mobile to tablet to desktop to desktops and in-between. You want to provide best of the breed in terms of performance and flexibility and nativeness; but indeed you want to keep up the good developer productivity. So what you come up with? A multi-flavored beast in my case. The product I’m maintaining is actively being developed, being backward compatible with dozen+ existing platforms, multiple form factors, and still look classy (look’n’feel is not everything but it’s something that makes sell things easier – old saying but does apply). Sometimes we are bending hard to bring in existing (legacy) codebases with ease (ease from the side of providing the backward compatibility to bring them over and the automatic live conversions to make it look and behave like the rest of the modern application pieces we have), but the flexibility we achieve on being able to bind together message buses from different platforms transparently pays off very quickly. If you are interested in participating on dreaming up such a platform, don’t hesitate – the career site awaits you 🙂

Leave a Reply

Your email address will not be published.