GAE-Studio is now open source!

Some of you may already have noticed or heard me saying that GAE-Studio was going to be open sourced and I think it is past overdue to officially announce it: GAE-Studio is now open source under Apache 2 and freely available! We promise to keep working on it, and to make that possible, we’re going to add GAE-Studio support to our open source support packages. You can find the source code under our Arcbees github organization as well as on maven central. We released an official, stable version 1.0 a couple of days ago that you can see in action on our demo website. You can also read our documentation to learn more about how to install GAE-Studio in your Google App Engine application.


Some may wonder why we chose to open source what was going to be our first official product. We’ve first started this venture almost 3 years ago when Arcbees was still in its inception. We were using Google App Engine heavily, and the lack of a good datastore admin console was a big problem. At the time, Google App Engine didn’t have any hooks on which we could build one, so we hacked our way around and built something useful for our own work. One year later, after finding other users were feeling the same pain as we did using Google App Engine, we set out to improve GAE-Studio user experience. It was planned to be our very first product that wasn’t going to be open sourced.

Last summer, Google IO announced a new console for Google App Engine that removed much of the pain that GAE-Studio was designed to help with. Then some time later, Objectify-Insight came out, and our visualization engine would be in competition with it. Since we love and have been using Objectify for years, we didn’t want to become their commercial competitor.


Still, we were and are hopeful that GAE-Studio will be useful for our developers. For one thing, GAE-Studio is available to all environments using the Modules, although it was initially written for the Java runtime. This is because Google now provides hooks in the Google App Engine SDK for the things we had to hack our way around to in the past. The further advantage of GAE-Studio is that it can be used locally! While Google has improved the usability of their cloud console a lot, the usability of local development tools is still weak.
Several hundred users have expressed an interest in using GAE-Studio, and we are now ready to officially release it in their hands. We hope you will find GAE-Studio useful, and will help us support the remaining runtime.

Thanks for the support and words of encouragement, and thanks for sticking with us through this venture!

About GAE-Studio

GAE Studio helps you optimize applications hosted on Google App Engine.

GAE Studio also allows datastore exploration, modification, deletion, import and export. Think of it as your swiss army knife for developing GAE applications!

Using real-time analysis of datastore requests, GAE Studio quickly highlights inefficient queries and gathers metrics that will help developers improve application performance.

GAE-Studio reaches V 1.0 and now supports all App Engine programming languages!

It’s a big day for GAE Studio. Version 1.0 has finally arrived! The software is ready for use by a much larger segment of the GAE development community. It is now possible to use it with every language that App Engine supports!

To get started, you only have to read our documentation. Now, let’s dive in and see what’s new in version 1.0 of GAE Studio.

Screen Shot 2014-07-22 at 11.17.16 AM

For all you GAE developers who create applications in languages other than Java, GAE-Studio now supports Python, Go and PHP. This is a big step forwards for our product. Supporting all available runtimes has always been one of our objectives, and we know it is a capability many people were waiting for. To make multi-language support possible, you can now use GAE-Studio as a module. Using GAE-Studio locally will be a challenge, but we’re working hard to make it easy to use GAE-Studio. Using it locally with Java is already possible if you build an EAR. We’re working hard to make this process as seamless as possible in every runtime.

The login/oauth system was a hassle for first-time users. Since we want to put this software in as many hands as possible, authentication and license validation has been removed. You still need to login with your developer account to use GAE-Studio as a module. This change comes at a cost, in order to keep developing GAE Studio, we need to sustain an income, so we have moved some features to the paid tier. Once we’re ready to re-introduce them, you’ll be able to purchase a license to activate those features. We’ll talk about them in detail in a future newsletter, but just as a snapshot here’s a list: profiling datastore requests, applying batch operations on large datasets and evaluating GAE usage cost.

We also installed GAE-Studio on a really simple sandbox application, which will allow you to try it and quickly see if that’s what you need. There’s a Submit form if you want to help us fix any problems you find, or to send suggestions to improve the product. You’ll need to request access to the sandbox by sending an email to:

Also, GAE-Studio will now let you execute GQL requests to filter data. It is a powerful tool for extracting only the data you need for a given development task.

Screen Shot 2014-07-22 at 11.29.13 AM

We’ve added visual cues based on beta tester feedback, and we think this really improves the UX. We ourselves use GAE-Studio every day for our projects, so we really understand and appreciate the value of these UX improvements.

After adding JSON import/export in our last release, we now feature the ability to export to CSV, which can be useful if you want to use analytical tools like Excel to examine your data.

Screen Shot 2014-07-22 at 11.29.55 AM

Last but not least, you can now select multiple entities and delete them, or mass-edit the values in fields that selected entities share.

Screen Shot 2014-07-22 at 11.31.01 AM

Please continue offering us feedback via our issue tracker, or drop us an email ! This was a big release, but more and better things are yet to come. We are really looking forward to our upcoming releases and want to incorporate your feedback in the process. Thanks for all your help so far. You are all awesome and please join our community on Google+ to follow progress as well as exchange ideas with other developers.

To conclude this newsletter, we should not forget that building software is a collaborative enterprise and we have many contributors to thank. You should pay attention to those names, because these people are awesome and have mad skills! We are deeply grateful for their work. Thanks so much!

Contributors (since the first commit in 2011)

Alexandre Breton
Brandon Donnelson
Christian Goudreau
Christopher Viel
Gael-Jurin Nkouyee
Jason Lemay
Javier Fernandez-Ivern
Jean-Christophe Larivière
Joël Trottier-Hébert
Julien Dramaix
Manon Gruaz
Maxime Mériouma-Caron
Mrabti Idriss
Olivier Lafleur
Simon-Pierre Gingras
Vincent Roseberry

The bees need your thoughts on GAE-Studio!

As our product evolves, we rely on frequent feedback from users to stay aligned on what you really want and need as developers.

We want to make a tool that will help you be more productive and drive down development costs.

We would really appreciate it if you would take a few minutes to help us by filling out the following survey.

Thanks so much! It really means a lot to us. We pay enormous attention to every idea you share.

GAE-Studio Newsletter #6

The agile Bees are working really hard to develop the best tool ever for working with Google App Engine. We want to make using the GAE stack easy and fun. We’re happy to announce the release of GAE-Studio 0.8.1, the latest version of our rapidly evolving GAE development environment !

What to expect in this newest version?

We have completed the redesign of the application that we initiated a few weeks ago. We also added a logout button and tweaked some of the feedback/error messages to improve your user experience, which is always important to us.


At a technical level, we have added a much-requested feature : the ability to import and export data from Google App Engine. At the moment, there’s an import limit of 2 Gb, due to the limitations of GAE Blobstore, but within that limit the import/export feature works. Additionally, we fixed an issue with the prior version of GAE Studio which did not allow people to activate email addresses containing a “+” character.

A quick warning note : we’re planning to refactor our authentification API in the next iteration of GAE-Studio, so when we will release 0.9, you will need to update to the newest version.

As usual, thanks for reporting any issues that you find when working with GAE Studio. That feedback is our most powerful resource for making the software better. We’d love to hear more! If you have a few minutes today, please let us know what you like most about GAE-Studio, what you like least, and what features you’d like us to add. We appreciate your advice. Drop us an email or use the issue tracker to let us know what you think.

Thanks a lot and we look forward to your feedback !


GAE-Studio Newsletter #5

(Version française à la suite)

Good morning fellow developers !

In business news, we greeted yesterday a new bee : Joël Trottier-Hébert, who will enhance our team by focusing on integration tests in our projects, including GAE-Studio.

In product news, we’re proud to announce our first version of GAE-Studio for 2014, GAE-Studio 0.7 !

We have started releasing GAE-Studio to Maven Central, a long awaited feature, which will be a lot more convenient than downloading a jar for every new version. 😉

You can already find our newest version on Maven.

On the functionality side, we switched from RestyGWT to RestDispatch. We also added a lot more user feedback to the UX, which we think is really important when developing something that we want people to use a lot and often.

As promised, our new UI is really kicking ass. Please tell us if you like it ! It’s a work in progress, but we think it’s moving in the right direction to make GAE-Studio an application that will be easy and fun to use.

Also, we’ve sent a new wave of invites to the  GAE-Studio beta group. We now have quite a few of you and we really appreciate the feedback that we’re receiving. Please continue to send it !

If you have suggestions or issues, let’s talk in the issue tracker ! We really look forward to any opportunity to provide help or be of service.

Here are a few screenshots of the new user experience. Give it a try today ! You won’t regret it.

visualizer profiler


Bon matin à vous, chers développeurs!

Tout d’abord, une nouvelle d’entreprise puisque hier une nouvelle abeille s’est jointe à nous, soit Joël Trottier-Hébert. Joël ajoutera une plus-value à notre équipe en se concentrant sur les tests d’intégration de nos différents projets, dont GAE-Studio.

Ensuite, côté produits, nous sommes très fiers d’annoncer notre première version de GAE-Studio de 2014, GAE-Studio 0.7!

De plus, nos nouvelles versions sont maintenant disponibles sur Maven Central, une fonctionnalité attendue depuis longtemps. Beaucoup plus pratique que de télécharger un fichier .jar à chaque nouvelle version. 😉

Vous pouvez déjà y retrouver notre version 0.7.

Côté fonctionnalités, nous sommes passés de RestyGWT à RestDispatch. Nous avons aussi ajouté beaucoup de feedback à l’expérience utilisateur, une modification essentielle pour quiconque veut que son produit soit davantage utilisé.

Tel que promis, notre nouvelle interface usager est vraiment superbe. Merci de nous dire si vous l’aimez ! Ce n’est qu’un début, mais nous pensons que nous sommes dans la bonne direction pour faire de GAE-Studio une application agréable et facile d’utilisation.

Aussi, nous avons envoyé une nouvelle vague d’invitations à GAE-Studio. Nous avons constitué une bonne liste de béta-testeurs et nous apprécions réellement les commentaires que nous recevons. Continuez à partager avec nous!

Si vous avez des suggestions ou des problèmes, n’hésitez pas à le mentionner dans notre gestionnaire d’incidents. Laissez-nous vous aider!

Voici quelques captures d’écran de la nouvelle expérience utilisateur. Essayez GAE-Studio aujourd’hui. Vous ne le regretterez pas.

visualizer profiler

GAE-Studio newsletter #4

Good morning GWT and GWTP fans !

In celebration of the GWT.create Conference, we’re launching three new releases in the next few days. If you’re attending one of those two conferences, Christian Goudreau and Julien Dramaix (two of our Bees) are looking forward to see you in person !

Today, we’re launching a new version of GAE-Studio, our kickass Google App Engine tool. Monday an IntelliJ plugin for GWTP is rolling out for all you IDEA fans out there, and next Tuesday, “tah-dahhh!!!” …a new version of GWTP will be released.

But today, we’ll dig into the newest features in GAE-Studio 0.6 – which we have just released along with a new wave of invitations so more people can join the party in progress!

First of all, let’s extend a warm welcome to our new UX designer, Manon Gruaz.


She did an amazing job redesigning our login page and she’s just started a complete redesign of the GAE-Studio GUI (visualizer and profiler). She’s going to make our tools look awesome through her own individual style of magic.

Under the hood, we have integrated our new licensing system with GAE-Studio. This was announced earlier. For the moment, we only have one beta key, which is 0aa490b7dacaf078d8f3111f1dec7253. You can use that for as long as you continue to beta test the software.

Moreover, we’re now using the Channel API (websocket) for the profiler. It will be more efficient in terms of resources. As usual, we fixed a few bugs as well in this release, and solidified our tests. In case you were wondering, you can now use String Ids without any problem.

We have also fleshed out and improved the design of JSON entity editing. You can now use any Objectify type in your Google App Engine application.

That’s it for this GAE-Studio release. Tune in to our blog monday for the official annoucement of the IntelliJ IDEA plugin !

Jukito 1.3 and GWTP 1.0.3

Like good gardeners, we are always cultivating our software, helping it to grow and develop.
We listen to your comments and try to evolve our software to meet your needs.
A few days ago, we released two new versions of our Open Source projecs.

Some of you may have noticed already, but we also removed the donation link from our projects. Not because users didn’t use it, but because we want to show everyone that we @ ArcBees want to fully support that project onward! We received an enormous amount of contributions in the past years either as code contribution or money donation. For that, we want to thank EVERYONE! Not only the contributors, but also the users to make this happen!

THANK YOU, from everyone @ ArcBees.

Now, here’s the details of the fixes and the new features.

Jukito 1.3

– A fix for issue #26 (Do not use un-annotated bindings)

Updated copyright to 2013

Add Samples

Descriptions on test & nice test names in IDE

Fix checkstyle and comments

GWTP 1.0.3

– A fix for pull request #312 (Custom ActionException subclasses are not rethrown as new ActionException)

Support APT processor with Java 7

– Fixed integration tests here and here.

Added chromedriver to README

To all contributors on these releases, thank you !

Special thanks to ahri, branflake2267, christiangoudreau, Chris-V, kuhnroyal, meriouma, przemekgalazka and spg !

GAE-Studio newsletter #3

Good morning, awesome rockstar superhero beta-testers !

The time has finally come to send out yet another round of invites and launch version 0.5 of GAE-Studio. Our product is becoming more and more stable thanks to the technical prowess of our top shelf geeks.

What’s new in this iteration? Mostly stability improvements (the team added a lot more tests) and interoperability with JSON objects. You will now be able to modify JSON objects in a form, instead of in a textarea. This should reduce errors and make the process easier. Also, we added a login to the ArcBees server, so that we will be able to integrate GAE-Studio as a Maven dependency really soon. Finally, a few UI improvements (dropdowns) and bug fixes complete this fabulous release.

What to expect next? We will integrate a new licensing system that will be used across all of our future software products. Also, we will be able to edit the various elements that are stored in Objectify more easily. Finally, a new artist is joining the team, to make GAE-Studio as professional as it can be, in form as well as function.

As usual, stay tuned to the Bitbucket issue tracker, and never hesitate to share your  successes, troubles or funny stories related to using GAE-Studio!

Working with you is always fun. Keep the feedback coming so together we can build the ultimate, most incredible, most powerful  tool for GAE developers everywhere.

GAE-Studio newsletter #2

Good morning, kickass GAE-Studio beta testers!

We’re excited to be releasing our next version of GAE-Studio. Our last iteration of testing went great, and we were able to enable a new GAE-Studio feature. For those of you who were in our first group of testers, we want to thank you for the time you put into GAE-Studio, and the feedback you have given us. We hope you and all you new testers who are joining us will push GAE-Studio even harder this time around, so it can evolve into a tool that will really make all our lives easier when it comes to managing Google App Engine development.

In this release, we’ve worked to enhance the visualisation tool, and we have also enabled the profiling tool. You’ll experience fewer bugs and will be able to integrate GAE-Studio with even more projects! The profiling tool itself will be completely reviewed to be more useful, but by activating the current version, you can already use it to see what is being pushed into the datastore as well as what is being pulled.

The ArcBees team has been working very hard, and most of them are going to head out for awhile on some well-earned vacations, so the upcoming iteration will be a really simple one. We’ll be working on a new authentication service for GAE-Studio that will let us operate it more like SaaS. In the future, we plan to release GAE-Studio as a commercial product, but it will remain free until all of you are satisfied that the user experience and feature set it offers make it a true Pro tool.

We’re starting to think about enabling Python, Go and PHP. If you think this is important, please vote for the language of your choice on our Bitbucket issue tracker so that we can know what to prioritize when we start that.

That wraps up another GAE-Studio newsletter! As always, log your issues and feature requests right within our Bitbucket issue tracker. That’s where all the action is. If you’re starting to become a heavy GAE-Studio user, we want to hear from you! We’re ready for some pretty deep conversation and collaboration with heavy users. We invite everyone to get in touch with us and tell us how GAE-Studio is helping you, and what you would like to see added or improved. Join our GAE-Studio Community on Google+, and meet other developers working on the leading edge of GAE development. While the community is for discussing GAE Studio, the people you meet there can help you in all things GAE-related.

Have fun Google App Engine-eering!

GAE-Studio newsletter #1

Good morning GAE-Studio users!

These are exciting days for us at ArcBees. We’re getting tons of great feedback about GAE-Studio from you, and we really, really appreciate it. We’re also excited to launch this first edition of our GAE-Studio newsletter (in future editions it will be redesigned to look more and more awesome). But most importantly, we’re excited because we are already ready to announce a new release of our software: GAE-Studio 0.3!

Our focus for this release was to integrate GAE studio with other existing projects. We’re almost satisfied with the outcome, but there are still some things that need doing. In the next release, we will make GAE-Studio even more usable from projects using Java and will try to avoid as much as possible conflicts with your own versions of dependencies that you could be using. This will add a lot to the usability and serviceability of the offering.

Besides these improvements, we’ve also moved the whole system from RPC to a REST API. This change lays the groundwork for two things. First, it provides an API you can use within your own applications, and second, it becomes easier to use a language other than Java this way. Think about it, Python, Go and PHP are the three other runtimes used in Google App Engine and it is on our roadmap to fully support those runtimes.

Many more changes are in the works for later releases. There’s been a lot of interest in our Profiler, so we plan to introduce a preview of it to those of you in our current beta group. We will also work to make sure that GAE-Studio can be used from Google App Engine directly, replacing the current datastore administration console. To do this, we have to create several security features to make sure only registered users can access GAE-Studio. While we’re reading back what we just wrote… Someone of the team already did it and it is available through using Google App Engine native security feature!

We are moving to a three-week release cycle from this point forward, until the project stabilizes, at which point we will publish daily builds. I know that documentation is lacking right now, so if you have any questions or problems, don’t hesitate to let us know. We’ll get back to you as soon as we possibly can, and we are genuinely interested in anything you might have to say about the product.

That’s all for now folks! As always, I invite you to log issues and feature requests right within our public issue tracker on Bitbucket. If you’re extensively using GAE-Studio already, please get in touch with us and tell us more about how it is helping you, and what you would like to see added or improved. Finally, I eagerly invite you to join our GAE-Studio Community on Google+ . We have a great group of people using the product, and the best way for you to meet all of them is by joining that Community.

Have fun Google App Engine-eering!