TT Mobile showcase

My friends at TT are really busy trying to get the mobile clients out the door and into production. TT’s twitter account is buzzing with all kinds of photos and videos. I am really happy and proud of how far my apps have come. The end result is looking beautiful and I am sure the end-users will be delighted by both the design and functionality.

I really enjoyed working on TT Mobile, as it presented a very unique set of challenges. How to effectively push price updates over potentially slow cellular connections? How to ensure users don’t accidentally place trades (butt trading anyone)? And how to effectively integrate with the rest of TT’s eco-system? I think the team did a splendid job and the apps are rock solid. One disappointing fact is that both Android and iOS apps could have been released over a year ago, had we chosen to re-use logic. There are ways to write the code once, and use it verbatim on multiple mobile platforms (naturally the look-and-feel needs to be done separately, so that the app feels “native”). I have long argued with the executives and advocated for shared business logic, since it seemed like a no-brainer.

  • Shorter time-to-market. In today’s fast-moving world it’s imperative to be there first.
  • Lower cost of development.
  • Less bugs.
  • Parallel releases on multiple platforms.
  • Lower long-term maintenance costs.
  • Less testing effort.

Other companies are not as short-sighted and have long recognized the benefits of writing the common logic once, instead of re-implementing it for every platform. Xamarin has their cross-platform C#. Google is pushing Java with its ability to share code between Android, iOS and the web. Dropbox uses C++ for shared logic. RemObjects has their cross-platform Swift. Not to mention frameworks like Flash and Cordova. I still cannot believe that the decision makers would rather have us maintain two separate codebases, but I guess you need to be good at engineering to comprehend the benefits.   

On a positive note, I am extremely pleased with the aesthetics of TT Mobile apps; graphical design and usability are essential. Nobody wants to use an app that looks “f-ugly” or that feels cumbersome. Folks at TT spent countless hours doing usability studies and polishing the design. Trust me – a lot of love went into making of these apps. They look awesome, they are snappy and I really hope you’ll enjoy them 🙂

TT Mobile available in Google Play

TT Mobile is now available for everyone to download from Google Play. It looks awesome! Great job, team! This version also added support for trading strategies written in TT SDK running on my AlgoSE server. Below is a screenshot showing child orders of SSE’s Time Sliced order. TT’s next generation Synthetic Strategy Engine (SSE) runs on top of TT SDK and AlgoSE server. SSE strategies are written by my good friend William Baker.

Download TT Mobile today! 🙂

 

TT Mobile

TT Mobile now in Google Play store

 

TT Mobile in Google Play

Today marks an important milestone. TT’s next-generation mobile trading app for Android has been deployed to Google Play Store. It’s still in pre-release and available only to beta testers, but we are getting closer every day. It’s very stable and usable. The overall look has deviated slightly from my original design, but I like it better this way. It’s a little bit more intuitive. Below are the main functions of the app so far.

  • Watchlist of instruments
  • Instrument-centric view of orders and positions
  • Trading from order ticket
  • Trading and order management from price ladder (MD Trader)
  • Order management screen
  • Fills and Positions
  • Forever Audit Trail

The users can input trades from order ticket and MD Trader, monitor orders, have a watchlist of instruments, inspect their positions and watch the forever audit trail. Not too shabby for a mobile app! Very full featured, especially when compared to what’s out there. The team did an outstanding job. Oh, and iOS app is coming along as well.

If you have a @tradingtechnologies email address, head over to the link below and download your copy for Android.
https://play.google.com/apps/testing/com.tradingtechnologies.ntm
(pssst – can’t access the page? Make sure you’re logged in only with your TT account. Try incognito mode)

For those of you who don’t yet have access, take a look at some screenshots below.

Mobile project, cont.

Something I just thought of for my new mobile project:

I also want to reuse as much code as I can between the WP7 and Android solutions. The code sharing part is what in my opinion will be most complicated. It seems like the two “camps” couldn’t be further apart, and that there are no common tools available. It would be great if there was something like MonoTouch but for Android (MonoDroid, are you here yet?) so that I can code in C#…

Hopefully, with Brad Abrams working for Google, we will see a more .NET friendly Android. Time will tell. In the meantime, I need to figure something out.

Mobile project

Long time, no blog. My life has been pretty busy, which is why I’ve been neglecting the blog. It’s easier to just send a few tweets to share my thoughts. Tonight I have a few spare moments, so I decided to write.

In the past few weeks I attended many local coding events. Last Saturday was the Chicago Code Camp, then Silverlight design training with Adam Kinney on Friday, and the Chicago Android workshop yesterday. Needles to say, I feel overwhelmed by all the cool technologies out there. I wish I had the time to learn them all. I am especially thorn between the upcoming Windows Phone 7 and Google’s Android.
I really like the .NET Framework and the flexibility of Silverlight (for once Microsoft did a good job designing something), but I also like the openness and possibilities that come with the Android platform. Plus my phone runs Android, so it would be cool to know how to program for it.

I am thinking of doing a small app that would let me explore the two platforms a little bit more. I want to start with something simple, just to get my feet wet, before I move to something more ambitious. For my first app the plan is to explore transitions between screens and different list layouts. I will be sharing my experiences on this blog. If you have any comments or suggestions, please leave me a line.