First of all I would like to thank Davide, Alessandro and Marco for their amazing work over the past 3+ years in creating what we all know as the Baker Framework today.
It has grown and evolved over the years into an amazing product, community and solution for digital publishers all over the globe.
Just what has the team achieved in this timeframe?
- 10 releases – one every 4 months
- 310 forks
- 16+ contributors
- 941 commits
- 14,901 lines of code
- 60+ new publications
- 20,000+ downloads
- 200,000+ people reached
This is an amazing accomplishment that deserves recognition!
I myself have been involved in the project in various ways over the years, in particular around the time that Newsstand was being pushed out by Apple. I realized the potential of the Baker eBook Framework and spent a lot of time working on a fork of the pre Baker 4.0 codebase that provided Newsstand and Shelf capabilities. A handful of publications made it on the App Store using this fork and I learned a lot about the Newsstand system.
When the Baker Team finally started their push to add Newsstand support into the mainline Baker Framework, I jumped in and helped where I could as I realized that there was much opportunity in Baker by supporting Newsstand (and not just standalone eBooks). Fast forward to the 4.0 release which gave publishers an amazing opportunity to create Baker Based Newsstand applications with Free Subscriptions!
Around the time this was happening, I corresponded a lot with Davide and the team about the direction of Baker and the next steps towards Paid Subscriptions. This opened up a whole can of proverbial worms due to the fact that in order to support Paid Subscriptions, publishers would need to host their own server backend in order provide the necessary functionality for Baker to work with the Paid model. This is when I started to conceptualize MagRocket. MagRocket was developed and I worked closely with the Baker Team on defining an open API so that Baker could have a method of talking to any custom backend server - not just MagRocket. I also committed to making MagRocket Open Source and aligning my development to coincide with the Baker 4.1 release in May of 2013. My initial goal with MagRocket was to provide the basic functions required by a server component so that publishers could easily implement on commodity hardware (Linux, PHP, MySQL) and support Free and Paid subscriptions and Paid Issues.
Many of the Baker Applications today in the App Store that offer Paid Subscriptions and Issues are using MagRocket. I've had the opportunity to work personally with many of the familiar faces on the Baker Github Community in implementing MagRocket to support their applications.
Up until a few weeks ago, I had been merrily working away on various MagRocket initiatives...until Davide approached me about becoming the new Baker Product Lead.
How could I turn down such an opportunity? It was an easy answer. I was immediately excited about all of the possibilities! Many of the ideas that had floated around on pieces of paper and in my head regarding MagRocket suddenly took on new life. Things that may have been difficult to accomplish from the outside all of a sudden seemed possible...
I am excited to share some of my ideas with you all. Things may change as we move forward. Wait, I'll rephrase that. Things will change as we move forward. Hopefully as you will see - for the better of all involved in this community and product.
My Baker Vision
I'm going to cheat a bit here because much of my vision for the future is based on what Davide, Alessandro and Marco set out 3 years ago to do. We will continue to "make high-quality digital publishing open to everyone". I think that simple idea will still be the cornerstone of all work going forward.
I want to get to the point where Baker is discussed as a viable and compelling alternative to Adobe DPS, Mag+, etc... Not because it's less expensive to get started and develop digital publications... But because it blows the other options out of the water!
I always think about this quote from Steve Jobs when I set out to do something in my life.
We’re here to put a dent in the universe. Otherwise why else even be here? Steve Jobs
My goal with Baker is to "put a dent" in the digital publishing universe... I want people to look at our product and compare it with things that cost thousands upon thousands of dollars to purchase, yet sit in amazement and wonder how they can get something just as (if not more) powerful and flexible for such a low cost.
So how do we as the Baker community put a dent in the digital publishing universe?
Well, to start - here are my thoughts on a few different areas and new initiatives that you will start hearing and seeing more about in the coming months.
As Davide alluded to a need to streamline the process of Newsstand publishing with Baker. Much of my work on MagRocket will move to a more Baker Framework focus and MagRocket as a standalone product will be phased out.
One thing I want to make perfectly clear is that Baker itself will remain Free and Open Source under the BSD license terms. Baker API's will continue to be generic and accessible to Third Party Developers. It is not my goal to close any doors of opportunity with the platform, it's quite the opposite. I want to continue to build a community of developers and partners that strive to make Baker a premier publishing platform!
Baker Branding
To mark the transition to our exciting future, I'm planning on rebranding the Baker suite of products... You will start to see the new logo and mark being used across the various marketing collateral, GitHub, Twitter, and the Baker iOS project in the coming weeks. We will be keeping some continuity by leveraging the "B" mark as part of the future brand :)
Baker iOS Application
I see work continuing on the Baker iOS Application with various new features and enhancements to continue to be competitive and create a compelling end user experience.
I will be looking for suggestions and be doing some work to identify key opportunities to implement features that bring the Baker iOS product to parity with some of the highest rated $$ frameworks out there.
There are many features requested in the current Issues log, these will be reviewed and slated for future releases etc.
.HPUB will continue to be the standard going forward.
Baker Cloud Console SaaS
One of the things that I have always thought was missing from the Baker Framework was a hosted backend offering that is easy to use by developers and publishers. What I'm talking about is a simple offering that supports the required server side functionality to deliver an end to end Baker application. I envision a future where a developer can download the Xcode project, hop on over to the Baker Cloud website to register for an account and immediately be able to start developing and working on his/her project.
In today's world, the developer would need to go through the hassle of setting up their own server backend (if wanting to develop paid subscriptions) and deal with web hosts, .HPUB storage etc... All before really being able to get going.
The Baker Cloud Console will solve this issue. Much of my work with MagRocket will be leveraged in creating the Baker Cloud solution which will offer all the basic functionality for a developer/publisher to get their app from development to production.
I want to emphasize though that this solution still will require someone having their own developer account, Xcode knowledge and .HPUB creation skills. It will be a nuts and bolts implementation to as simply as possible build an end-to-end infrastructure.
Pricing will be simple and affordable. HPUBs will be stored and served from a solution such as Amazon S3 or Dreamhost DreamObjects. TBD
Other solutions offered by Third Party Developers and Companies might take this a step further and offer value added solutions that go beyond what the Baker Cloud offering will supply. That is great! I want to foster a marketplace of offerings that fulfill the various levels of people interested in publishing on the Baker Platform. There are many exciting opportunities! However I believe that it is essential for the goal of "putting a dent" to have an offering with full support of the Baker Framework team be available!
Baker Cloud Console (CE)
So you don't want to use the Baker Cloud Console? You want to host your own backend and tinker around with Linux servers?
:) The current Open Source version of the MagRocket Administration Console and API will be rebranded as the Baker Cloud Console (CE). CE stands for Community Edition.
I will plan on making some enhancements etc going forward on this product, however much of my focus will be on the Baker Cloud SaaS solution.
The CE product will continue to support the minimum requirements for managing and providing Free/Paid Subscription support for the Baker iOS Application.
Baker Partnership Programs
This is one that I'm really excited about. I want to create new programs and affiliations for Developers, Partners and Supporters of the Baker Framework.
Like many programs that exist for other technologies and platforms - these opportunities will give Developers and others Third Party Partners various ways to get involved with the Baker Project.
I'll definitely expound more on what this means in the future.
The Baker Market
I envision creating something similar to "CodeCanyon" or the Envato Marketplace for Baker related goods.
Developers will have the opportunity to sell various goods in an official "Baker Market".
What types of goods am I talking about? Things that initially come to mind are Shelf Graphic Skins, HTML Magazine Templates, in5 Templates, Custom Code Libraries, other value added content creation assets, etc...
This is one way that I feel can enhance the adoption and excitement around the platform!
Wow, I think I typed way too much. I don't want this to become some sort of manifesto! :)
In closing I just want to again thank the Baker Team for this opportunity and for the passing of the torch for this exciting and compelling product. They have offered to remain associated with the project as Advisors and I definitely welcome their input on future strategy and planning.
Look for more information in the coming weeks as we get things situated in the new GitHub repo!
Regards,
Andrew