Rickard Elimää

Developed an AR solution.

Found over 500 issues in an upcoming parking app. Gave feedback on GUI, UX and gave advice about common usability while finding critical bugs and optimizations. Created a user case document and wrote UI tests based on that. Also got into the iOS app and fixed about half of the bugs reported for that platform.

Touched up the UI and fixed memory leaks and broken UX experience for this radio station. Updated the android app for new security regulations in later version of Android OS.

Creating an AR solution for a museum, where the visitors are using web based AR to enhance their experience

A server that updates a screen, and pings users in Slack to remind people to bring out the garbage. Work mainly consisted of doing minor UI updates, double checking and refactoring the code, and update the code that broken when NSR (the host) changed their API.

Took over a android java project, where a user can make a video, send the video with transcription to multiple recipients, and have the transcription translated to the preferred language of the recipient. Fixed multiple bugs, updated the increased usability of the app, cleaned up the design, added code to clean up Amazon S3 bucket, and updated the API. Distributed the app via Microsoft Intunes.

A display for a 3D printer. The work consisted of cleaning up code and UX while diving into the backend written in Node.js.

The app communicated with a backed in order to register tags in order to scan them against an NTC reader. Worked with both android and iOS and created an UI from scratch.

Adept Play needed a graphic designer to put together illustrations, fonts and text into a 400 page book to be printed. Included making a cover and additional appendixes. Worked closely with the client, made estimations, several iterations of each chapter, made photo manipulations of existing images, and produced a pdf file to be printed.

As the world cup in football was going off the staple, a new game was taking form on the betting site, but the planning, design, and backend development dragged on, leaving no time for frontend. Both Rickard and the other developer sat down and plotted all the new functionalities so they could prioritize what really had to be done, and what could be implemented after the first release. They came to the conclusion that they had to do 10 weeks of work in a month. There was a lot of work under stress, but the hard planning paid off and the new game could be deployed a few days before official release.

The Polymer version was outdated and the site could stop working. In order to upgrade to the final version, because the framework Polymer wasn't under development any longer, there was a need to understand the basic foundation of all one page frameworks that exist today, from React and Vue to Polymer and Lit. So Rickard took on a smaller private project in order to better understand webcomponents. The site had 600 files that needed to be updated, and the provided script from the developers of Polymer couldn't go all the way, so many of the files had to be handled manually. An additional script was written to cope with this. Two weeks later, after wrestling with build scripts, the site could be deployed to production.

The betting site took a new approach and went from B2C to B2B. Main responsibilities were to implement Facebook ads and handle integrations to have FSport's betting site for other sites, like TV4 among others, while customizing the site for their needs and customers. Reading API:s, setting up specific configurations for the site, and customer communication was a daily routine. Also implemented user feedback on the site by setting up web hooks in Slack, so we could instantly see how new features were received.

The code base for both the android app and iOS app were too old, so it was time to throw everything out and rewrite both apps from scratch. At the same time making them less independent of UI updates on the website. The solution was to take in data from the site and then dynamically change the apps so they didn't need to go through a deployment if parameters on the site changed.

The betting site grew more and more, and it was time to take a step back and reevaluate the original design. As time went on, the programmers added more and more functionality but at a cost of the user flow and usability. A new design where therefore necessary, which was first prototyped, tested and then developed further until it could be implemented on the site and shipped to production. Created a new theme for the site with the intention of increasing the usability while setting a foundation for making it easy to add more and more games and B2B customers without having to be a graphic designer.

Maintained the apps to include the new updates. Constantly had to switch between web and apps for every update, and make sure both the android and iOS apps were up to date. Icons changed. Functionality was added. At this time, Google Store didn't allow non-American betting apps so the users could only install an apk from the site.

Implemented two more games on the betting site, and had to work out the workflow, UI and functionality. Did a lot of playtesting and took the original version of the first game and made it into something more general, so it would be easier to implement new sports on the site as it grew. Were also responsible for localization during that time, where new languages were constantly added as the site targeted new countries and had more collaborations with other betting sites.

Took over a project that had been passed through two previous consultant companies. The code was a mess so it had to be slimmed down, through refactoring, optimization, and throwing out outdated frameworks. The first week, the app went from 60Mb to around 10, while getting increased network stability. Worked mainly on their iOS app but had to co-program with a colleague that worked with their android app. During the time, Vethem developed their website in React, and decided to continue with that code base for all apps using React Native which we, on the native apps, had to prepare the apps for before handing over the project.

Took the role of cleaning up the UI and analyzing the user flow, and made sure to implement a new design from an outsourced graphic designer. Set up Google Tag Manager, and analyzed data from Google Analytics in order to understand the user flow and where most of the customers dropped off. Attended a year-long course during this time, where he learned more advanced android and iOS features.

Came in on a freshly started betting site. Implemented new features while making the site data persistent. The main responsibilities were handling live data from the server and making sure that all components on the one page site updated accordingly, making sure to cache everything that wasn't live data. The site used shady DOM, a previous version of shadow DOM, in order to have each component on the site isolated from another. Also implemented server side localization, where the previous solution demanded a deployment every time typos and rephrasing were made. The language files were then cached and only updated whenever the language file on the server changed. This was later on also used in order to be able to show and hide functionality on the production site, and give different texts depending on which B2B customer that used the betting site.