8 minutes

First published: June 7, 2016

We started working with our first ticketing client back in 2005, developing and maintaining their box office software. Here is just a partial list of what our team has done for this client in over 9 years: venue mapping (defining a venue, with possible different configurations for seat selection); ticket packages (i.e. season tickets, events with pre/post gatherings, theatrical series, musical series, and so on.); event promotion; memberships; patron CRM functionality; box office sales; web site sales; seamless website customization; advanced and custom reporting tools; advanced features for seat selection and ticket purchase (at the box office, online); advanced service for ticket delivery, printing and scanning (standard printed tickets, self-print tickets, e-tickets); fundraising and donation management; refunds and exchange functionality; and ticket scanning with Linea Pro and iPod Touch or iPhone. 

The Need

After Softjourn’s team helped Ticket River, an Elk River business unit, improve its sales rates, we received a new request to develop software for one of their other business units, We helped them add another service to their suite that would allow companies to sell customized tickets directly from their website. Their target audience covered three different countries—the UK, the US and Australia—, but all countries were running on different codebases, so maintaining them was time-consuming and inconvenient.

The best fit solution here was to internationalize the US codebase to other countries, so it would adapt to local distinctions and convert all necessary data automatically.

Another separate project was to rewrite their graphics editor from Flash to HTML5, so it would work seamlessly across multiple mobile platforms and devices.

The Solution

Project I: US codebase internationalization

It was decided to take the US code, which was much more advanced in architecture and features, and modify it to support additional internationalization. Moving the other countries onto this unified codebase made future maintenance and feature changes much easier. Geographical distinctions such as currency, measurements and some other system configuration features would now convert automatically based on the location, so that customers wouldn’t need to convert these data themselves.

In order to support differences between different locations on static pages, it was also decided to create a small CMS to hold different static pages for different counties.

Project II: Rewriting the ticket graphics editor from Flash to HTML5

Initially, the graphics editor for designing ticket stock was written on Flash, but this technology is becoming less popular and content written on Flash is not supported by Apple devices anymore. Since every business is going mobile now and the percentage of customers coming via mobile is growing, decided to rewrite the editor to HTML5 Canvas with Softjourn’s assistance.


  • OS: Windows Server 2012 
  • Language: C#, .NET, HTML5 Canvas 
  • Development tools: Microsoft Visual Studio 2014 
  • Database: MS SQL Server 2014 
  • Framework: ASP.NET MVC, ASP.NET web form, NHibernate, CSS/JS bootstrap, Angular JS

The Benefits

Project I: 

  • Faster and easier codebase maintenance
  • Changes and updates will take less time
  • System configuration adjusts to geographical distinctions automatically (currency, measurements, etc)

Project II

  • Graphics editor rewritten from Flash to HTML5.
  •  Editor adapted to all mobile devices and screen sizes.
  • Slicker design in ticket graphics editor.