Personal Capital Engineering Message Board › Reminder: "Shared Clients that Don't Share Code" This Wednesday
Redwood City, CA
Three years ago when we started this company, we knew we would be creating a multi-client architecture from day one. It was part of every architecture decision. Even though that has made our job more difficult up front, it has served us well as we've experimented with clients ranging from Flex, Firefox Plugins, Windows DLLs, HTML5 apps, iOS apps and most recently our new Android app.
There was a pivotal moment in our API and client architecture and design: we switched from thick clients that made only a few API calls to get the raw data and then transform it to thin clients that relied on the server to do all the data transformation, aggregation and calculation so that our client developers and our clients could laser in on data visualization.
What was behind this pivotal moment?
We would like to discuss the thoughts and experiments that went into answering this question in our first meetup with you.
We'll also share some pizza and beer, because we're friendly like that.
See you Wednesday @ 7pm!