Company

System: Web application to display an interactive 3D animation of a truck loading a specified shipment

Client: Private

Technologies: .NET core, C#, Blender, Three.js, SQL

Problem: Create a web application which loads details of a user-specified shipment from a database, and depicts that shipment loading in a user-interactive animation.

Solution: This project integrates a number of separate areas of software engineering, including web development, 3D modelling and dynamic animation. The truck trailer with backgrounds and skybox were modelled in Blender, together with the Cargo bay and truck door opening animations - and these were imported into Three.js. Camera zoom and rotation were enabled using OrbitControls.js. The cargo box loading animation was created in Three.js directly using suitable vector mathematics, and the system mounted in a .NET core based framework. Specification of the shipment to load is provided by the user via a web form.

System: "SuperGraph" Native Android App

Client: John Adams Ltd.

Technologies: Java, Android, XML

Problem: The app had been removed from the Google Play Store due to a reported stability issue. There were also problems with accessibility of some buttons on smaller screens.

Solution: Several minor fixes were implemented including build parameter and file format updates, and layouts were corrected to make missing buttons visible on smaller screens. Updates were tested on multiple emulators using Android Studio. The app was successfully redeployed to the Google Play Store, and a report produced detailing the changes.

Before:

After:

System: Distributed web-automation application simplifying tasks on a public sector ecommerce portal

Client: MePATool

Technologies: Perl, Javascript, Mojolicious, Hypnotoad, SQL

Problem: The workflow required for public sector ecommerce in a particular jurisdiction can slow down business.

Solution: 7 subsystems have been created and are maintained by Virtual Blue, including client executables, API, Web Admin and web-automation processes. Multithreaded headless Chrome instances are controlled via a custom process management system. Rendering browsers tend to be memory hungry which is one reason the system is distributed across several servers, in order to cope with traffic spikes. Recently very low error rates have been achieved.