Monday, October 28, 2013

F2 at the FinTech Hackathon

Next Saturday and Sunday F2 representatives from Markit and Markit On Demand (MOD) will be attending the FinTech Hackathon event in New York City. The two-day event features some of the best and brightest designers and developers from financial services firms competing to build innovative solutions. MOD is participating as a Technology Partner and is offering a Raspberry Pi and Pebble Watch for best use of its APIs. We will be using the opportunity to discuss F2 and how developers can leverage the framework to deploy more F2 apps in more places. In addition, we'll be competing ourselves to create an F2-enabled solution using an inventive blend of Tech Partner APIs.

If you, your colleagues or friends will be in NYC Nov 9-10, sign up for the event—it’s at MongoDB headquarters and only costs $20 to register.

See you there!

Wednesday, October 16, 2013

F2 Turns One!

Happy birthday, F2!

One year ago yesterday we launched F2 and introduced to the financial services community a brand-new way of integrating tools and content from multiple providers into a single, seamlessly integrated front-end. Since last October, the F2 community has grown to include some of the financial industry’s biggest firms. Led by F2 Advisory Board members, these participating firms are demanding websites that are fast, versatile and built upon standards and open-source technology. Being efficient, iterating quickly, reducing time to market as well as complexity without compromising security are no longer dreams of product and technology owners; they are facts of life. The growing F2 team at Markit On Demand (MOD) continues to work hard to ensure the framework is easy for technology teams to adopt, simple for developers to follow, and modern for today’s savvy and demanding users.

These past twelve months have been very busy on many fronts. When F2 launched MOD were the only ones using the framework. Today between fifteen and twenty financial services firms have deployed F2-enabled solutions. Beyond simply using it, many of them are contributing to the evolution of the standard as well. The roadmap has seen eight revisions. One hundred forty-one Issues have been opened based on community feedback. F2 was initially released under the terms of the MIT license before switching to the Apache license in version 1.2. This change affords better protections to those working on centralized and contributed open source code. In short, we’ve made a lot of progress.

Here is F2 by the numbers to-date:

  • We’ve released fourteen versions of F2, the latest, 1.3.1, yesterday.
  • We’ve closed 120 GitHub Issues.
  • We’ve committed 893 source code revisions on GitHub.
  • Code additions and deletions total 643,000 and 467,000, respectively.
  • The F2 Advisory Board firms shrunk by one then grew by two.
  • More than 13,000 people have visited leading to 40,000 page views. Impressive for a 24-page website.
  • Nine of the eleven F2 Advisory Board firms traveled to Boulder in April for the inaugural F2 hackathon.

Looking broadly at F2 use, many have come to realize that by shifting development efforts towards a common specification that allows for complete customization, everyone wins. Information providers, content owners, financial firms, media outlets, developers and technology owners alike.

In the beginning we didn’t know whether F2 was going to be successful or not. As a result, we deemed it an experiment of sorts. Given where the framework is today, I think it’s safe to say it has been a success. And we’re working very hard to ensure it remains one. F2 has recently moved into the purview of MOD/L which doesn’t change who is working on it or how it’s maintained. The organizational move simply affords F2 the attention it demands and gives everyone the comfort in knowing they’re not adopting a dying standard.

While F2 is young, it’s growing up fast. Version 1.4 is scheduled for release in late Q4. We’re working hard on a proposed version two implementation alongside a complete redesign of and its accompanying documentation. Discussions are beginning around a second F2 hackathon. We have F2 team members going to fin-tech conferences to evangelize and learn from what others are doing. The list goes on.

If the previous twelve months are any indication, the next twelve should be just as exciting. Thank you to everyone who has contributed to F2's success over the past year. Without the efforts of the F2 community, we wouldn’t have had much to write about today. We’ve said all along that the greater the participation in F2 the richer, smarter and more effective it will be as an industry-wide platform to help reduce labor, time to market and costs. Thanks to the community this is more true than ever.

Tuesday, October 15, 2013

F2 version 1.3.1

Today we are happy to announce version 1.3.1 of F2. This is a minor release adding only one new feature to F2's javascript SDK and a handful of documentation revisions. The single addition to F2.js is a new published event when apps fail to load. Issue #108 has all the details.

Please review the changelog for the complete list of updates in 1.3.1. You can also review pull request #138 and all closed Issues associated with the 1.3.1 milestone.

Any questions, concerns, or bug reports, submit an Issue on GitHub. Version 1.3.1 is available for download (zip) from GitHub.

Issue #141 is tracking the update of F2 on

Wednesday, October 2, 2013

An update on using AMD in F2

Since we originally posted this at the end of August, we've had a lot of discussion (41 comments, to be exact) on the topic of AMD in F2. I wanted to provide an update to say the conversation in #125 has slowed down while we shift focus over to #129—a more appropriate and longer-term resolution than originally envisioned. Head over to GitHub to join the discussion!