Joe Lang

As Leia grew over the years, the Unity Plugin became increasingly more complicated to handle old requirements and new.

I simplified our Unity plugin logic from 40 classes to 8 without breaking core functionality. Additional features were then prioritized and mapped for integration.

We now had a plugin that was simple enough to reshape for future needs without the overhead of old assumptions and tech debt.

After Leia acquired Dimenco, we needed one plugin that could work across all displays on Windows and Android.

With our new simplified plugin structure, I was able to abstract out all device logic and set two streams for firmware communication.

We now have one logic flow that worked on all supported devices, Android or Windows. Later, when we added features, no code needed to be duplicated.

Leia's Unity plugin releases were ad-hoc, breaking changes were commonly thrown into release updates, and bugs were not caught prior to releases.

• Daily standups were introduced to review tickets and status
• Jira tickets were connected to branches and Pull Requests, making context and code changes easy to navigate
• Pull request workflow was standardized, encouraging team collaboration
• CI generated test builds to verify PRs did not break core functionality
• I mapped out our release process and announcement process so anyone on the team can launch an update

The workflow for the entire team was smoother, bugs were caught sooner, and the SDK was matured.

Our automotive partners needed to test rendering possibilities on experimental displays.

I built a process for pulling display configuration data with configurable JSON files. With that data, I could make builds for these displays without official firmware updates.

I was able to make demos for our automotive partner's experimental hardware and support them with internal projects.

Leia Unity SDK only supported default rendering, blocking content from working on our displays.

I restructured our SDK to add catches and hooks into Post Processing, URP, and HDRP rendering pipelines.

Leia Displays work out of the box with all rendering techniques.

Our plugins were facing several critical issues that were affecting customer satisfaction and hindering the adoption of our technology.

I led a team of three engineers to address and resolve these issues promptly. Our goals were to fix existing bugs reported by users, introduce new features requested by our clients, and manage the release of internal content related to the Unity Plugin to ensure it met our quality standards and user expectations.

Our team successfully resolved all identified bugs within the projected timelines, and we introduced several key features that significantly enhanced the functionality and user experience of the Unity plugin.

Industry partners and business stakeholders needed to showcase demos with various devices not available on the market, including experimental automotive hardware.

I was the go-to liaison who scoped the needs of the project and unblocked any barriers to creating content.

Leia was able to foster stronger relationships in various industries and continue support for experimental devices.

Leia did not have a standardized communication process for letting developers know about updates.

• Worked closely with the marketing team to develop clear, informative content about the new features
• Forum Engagement: dedicated a portion of my daily schedule to actively monitor and engage in our developer forums
• Feedback Loop: established a systematic approach to gather and categorize feedback from the forums, including bug reports and feature requests
• Update Turnover: set up regular meetings with our development team to discuss the community's feedback and prioritize actions

This process encouraged active community engagement in driving product success and customer satisfaction.

Leia embarked on an ambitious project to launch our marketstore with over 40 games. These games varied in complexity and audience, requiring a nuanced approach to porting, testing, and launching to ensure they met our high-quality standards.

• Project Management: developed a detailed project plan outlining key milestones and deadlines for each game, using project management software to track progress, assign tasks, and manage resources
• Communication: established clear lines of communication with our publishing partners via regular update meetings
• Quality Assurance Collaboration: worked closely with our QA team to develop a rigorous testing protocol for each game
• Feedback Loops: created a structured process for sending update requests and bug reports to our publishing partners
• Launch Coordination: coordinated with publishers to ensure a smooth launch as games passed QA

This comprehensive approach led to the successful porting, testing, and launching of all 40 games within the projected timeline.