Professional Projects

AR Viewing Experience for 2024 Euro Cup - Apple Vision Pro & Meta Quest 3

Client - Deutsche Telekom AG

Budget - $73,000 USD

  • Directed a paid POC for Deutsche Telekom exploring how to deliver live Euro Cup coverage (hosted that year in Germany) on next generation AR platforms. The project was unusual in that it launched on Apple Vision Pro and Meta Quest 3 before either device was publicly available, built specifically for an audience of Deutsche Telekom's executive team. Coordinated a vendor and project team dispersed across multiple time zones to take the concept from idea to working demo on a tight, fixed timeline tied to the tournament schedule.

  • The main challenge was developing a live Euro Cup viewing experience for Deutsche Telekom on Apple Vision Pro and Meta Quest 3 before either device was publicly available. With limited access to the platforms, vendors and project team members spread across multiple time zones, and a fixed deadline tied to the tournament, we had to deliver a working proof of concept within a tight timeline while managing significant technical uncertainty.

    Approach and Strategic Decisions

    We explored multiple features, including gesture controls, social annotations, and multi-angle viewing. However, I recognized that adding too many features could increase development complexity and put the delivery timeline at risk. I pushed for a more focused approach, prioritizing three core areas:

    1. Streaming Quality: Prioritizing 4K streaming, low latency, and adaptive bitrate management to deliver a high-quality live sports viewing experience.

    2. Spatial Audio: Creating an immersive, stadium-like audio experience that demonstrated the potential of AR for live sports viewing.

    3. Reliability: Minimizing crashes and buffering during critical moments to ensure a smooth and uninterrupted viewing experience.

    We deliberately deferred secondary features, such as gesture controls and social interactions, to reduce implementation risk and focus development efforts on the core viewing experience.

    This approach allowed us to deliver the proof of concept on time, with zero major issues, and successfully demonstrate the experience to Deutsche Telekom’s executive team. It also validated the importance of prioritizing quality and reliability over feature breadth when delivering an innovative product under tight deadlines and significant technical uncertainty.

Canadian Broadcasting Corporation (CBC) Olympics 

Client - Canadian Broadcasting Corporation

Budget - $500,000 USD

  • CBC had two application which were already live, one application was for French speaking audience called TTV and the other in English called CBC GEM both served different catalog of content and were on Samsung, Comcast, Roku and Web.

    The team was tasked to create a Olympics section for both apps before the 2024 Olympics hosted in Paris. Team was expected to deliver and clear a testing phase run by the CBC team well before Mid July to ensure all platform vendors have enough time to update the in market build of the app with the latest version that had the UI entry point to viewing the olympics content.

  • The main challenge was delivering a consistent and responsive user experience across platforms with different hardware capabilities. Our development strategy was to build the application experience for Web first and then port it to the other platforms. While the application performed well on Samsung and Comcast, Roku presented performance issues, including lag and jittery navigation when users interacted with the interface.

    With the Olympics approaching and a fixed delivery deadline, we needed to improve Roku’s performance without compromising the live streaming experience, particularly the ability to deliver high quality Olympic sports coverage.

    Approach and Strategic Decisions

    We explored two approaches to address the performance issues.

    1. Collaborating with Roku on OS-level optimizations: We leveraged our existing contacts at Roku to investigate potential operating system level optimizations. One option was to throttle video quality or limit the amount of data being processed to reduce the device’s workload. While this could improve menu responsiveness and reduce system instability, it risked increasing video startup times and limiting the available streaming resolution. This trade off was particularly problematic for a major live sporting event where picture quality was a key part of the viewing experience.

    2. Developing a dedicated video player for Roku: To avoid compromising streaming quality, we pursued a platform specific solution by developing a new video player tailored to Roku’s capabilities. The goal was to improve application responsiveness while enabling the player to deliver the highest available streaming quality from the start, including high quality live Olympic streams.

    This approach allowed us to address Roku’s performance limitations at the player level rather than relying solely on system level compromises that could negatively affect the viewing experience.

Rogers City TV plus - Comcast Application (Hosted URL Application) 

Client - Rogers Communications Inc

Budget - $30,000 USD

  • Create the CityTV plus Comcast application which would offer different live stream channels that the Rogers team can configure from the Accedo A1 configuration that was used in the original development of the application, in this project we had to implement and extend some new features of the application, which was adding watching history continue watching swim lane that would store users partially consumed data per session for the application locally on the device in adding to supporting the Rogers team with submitting the Comcast application for certification. 

  • The main challenge was implementing a Continue Watching feature for the Citytv+ Comcast application that would allow users to resume partially watched content from where they left off. Since Rogers offered both live streaming channels and video on demand (VOD) content, we needed to ensure that viewing history was tracked accurately across both experiences without incorrectly recording live stream sessions as on demand viewing progress.

    The complexity arose when a user watched a movie or show through a live stream channel that was also available in Rogers VOD catalogue. In these cases, the application needed to recognize the VOD title being broadcast, capture the user's viewing progress, and display the same content in the Continue Watching section with the correct resume position, even though the user had accessed it through a live channel.

    Approach and Strategic Decisions

    We addressed this by leveraging content metadata and extending the existing video player's event handling logic.

    1. Tracking VOD Content Within Live Streams: We configured Rogers live stream channels to pass additional metadata identifying the VOD content being broadcast. This allowed the application to distinguish individual VOD titles within a live stream channel rather than treating the entire channel as a single viewing session or having the application perform searching actions for the VOD content which would impact the performance for the experience .

    2. Capturing Content Transitions Through Event Driven Processing: Rather than relying on periodic polling to check for content changes, we implemented an event-driven approach in the video player that listened for playback events and triggered metadata processing whenever a new VOD title began within a live stream. This enabled the application to identify content transitions and update viewing history as events occurred, without repeatedly querying for changes.

    3. Maintaining the Continue Watching Experience: We implemented local viewing history storage on the device to retain partially watched VOD content and its progress. This ensured that eligible titles appeared in the Continue Watching section with the appropriate resume position, regardless of whether the user had originally accessed the content through the VOD catalogue or a live stream channel.

    This approach enabled us to extend the application's existing functionality while preserving a consistent viewing experience across live and on demand content. Alongside the feature development, the project also involved supporting the Rogers team through the Comcast application certification process.

Stealth TV -  Leading Discovery Phase 

Client - Bob Baskerville TV

Budget - $80,000 USD

  • This was another video streaming application targeted for the Web, iOS, Android and Roku. For this project we were ask to perform a discovery phase and complete designs for the application for the different platforms while also establishing some of the technical integration details before beginning the development phase. 

  • The main challenge was preparing for a large scale video streaming application spanning Samsung, Comcast, Web, iOS, Android (mobile and tablet), Roku, and Fire TV. During the discovery phase, I partnered with another Project Manager to review the project scope, identify technical dependencies, and prepare recommendations so the team could move into development as quickly as possible once the project was signed off.

    As we reviewed the Statement of Work (SOW), we identified a critical gap in the client's existing infrastructure. While the client had an on premises content production setup, the broader content delivery ecosystem required to power the streaming application had not yet been fully defined. This included how content metadata would be managed, how video assets would be processed and prepared for distribution, how streams would be delivered to different platforms, and how the applications would retrieve and display the required content.

    Approach and Strategic Decisions

    Rather than treating discovery as purely a UI/UX design exercise across multiple platforms, we recognized the need to establish and explain the details for the underlying technical architecture and integration requirements before development which we sharing with the account managers to guide the business agreement for the project.

    1. Defining the Content Delivery Ecosystem: We mapped the key architectural components required to support the application, including a Content Management System (CMS) for managing content and metadata, video processing and packaging services for preparing streams, and a Content Delivery Network (CDN) for distributing video efficiently. We also considered how these components would integrate with the client’s existing on premises infrastructure and the application layer.

    2. Preparing for Development Readiness: Working alongside the other Project Manager, we consolidated our findings, identified dependencies and potential risks, and prepared recommendations to help the account and delivery teams align the proposed scope with the technical requirements. The objective was to surface critical infrastructure decisions early rather than allow unresolved dependencies to delay development after project sign-off.

    3. Establishing Cross Platform Requirements: Given the number of target platforms, we needed to account for differences in device capabilities, playback support, and application requirements while defining the technical integrations. In parallel, we worked toward establishing consistent user experiences across the platforms through the discovery and design process.

    This approach helped shift the discovery phase beyond interface design to address the foundational architectural decisions required to deliver a multi platform streaming product. By identifying gaps in the content delivery infrastructure early, we could provide the client and internal stakeholders with a clearer understanding of the technical components, integrations, and dependencies that needed to be addressed before development could proceed.

Sensical (Common Sense Media) - Kids Content Viewing Application, New Feature Development  

Client - Common Sense Media

Budget - $400,000 USD

  • This was a video streaming application designed for young children, with a strong emphasis on complying with COPPA and applicable data privacy regulations across all supported platforms. While the application was already developed for most platforms, additional team support was required to extend feature development and implementation across iOS, Android, Roku, and Samsung

  • The main challenge was managing the product roadmap under a fixed price engagement with an open ended scope of feature requests. The client had considerable creative freedom to propose new features and explore product improvements throughout the engagement. While this flexibility encouraged innovation, it required careful assessment of incoming requests, prioritization of development efforts, and clear roadmap guidance to keep expectations aligned between the client and the internal delivery team.

    An additional layer of complexity came from the application's target audience. Since the product was designed for young children, every proposed feature needed to be assessed not only for technical feasibility and development effort but also for its implications for children's privacy, data usage, and compliance with applicable regulations, including COPPA.

    Approach and Strategic Decisions

    We established a structured approach to managing feature requests and guiding the product roadmap while balancing client expectations.

    1. Managing Feature Requests and Prioritization: I introduced daily sync meetings with the client team to gather requirements, clarify feature requests, and resolve ambiguities early and quickly. I also established dedicated weekly sync sessions with the engineering team to address technical challenges, assess implementation complexity, and identify potential risks to development timelines. This communication structure helped ensure that requirements were clearly understood, technical dependencies were addressed promptly, and the roadmap remained aligned across stakeholders.

    2. Balancing Creative Flexibility With Scope Management: Given the fixed-price engagement, I managed the evolving backlog by assessing new requests and communicating their implications for development effort, priorities, and delivery timelines. This involved maintaining roadmap visibility, aligning expectations with the client and ensuring the clients signoff was involved before perusing any development activities. This process implementation ensured that the development and testing cycles were uninterrupted and provided clients the visibility of the products growth direction.

    3. Ensuring Children's Privacy and Regulatory Compliance: We considered privacy and compliance requirements during feature assessment, ensuring that proposed functionality accounted for the application's young audience. This was particularly important for features involving playback behavior, personalized recommendations, analytics, and user data collection, where implementation needed to align with applicable children's privacy requirements to hassled free feature rollout of app stores.

    Key Features Delivered

    The roadmap included several enhancements to the existing application, including deep linking directly into content playback, autoplay with recommended content and playback pause limits, live TV integration, new analytics integrations, and UI improvements across supported platforms.

    This project required balancing product innovation with structured roadmap management, fixed price delivery constraints, and the additional responsibility of building a privacy conscious experience for children. It reinforced the importance of establishing clear communication channels, evaluating feature requests systematically, and aligning client expectations with technical feasibility and delivery commitments.

Medical Research Project

Impact of Biofeedback and Personalized Nutrition on Glycemic Control, Multi-Omics Markers and Mitochondrial Health in Early Dysglycemic Individuals: A Stratified Randomized Controlled Trial.

Role : Project Lead & Coauthor

  • This study evaluates early interventions in prediabetic individuals. One group receives standard ICMR care, while the other adds continuous biofeedback tools for BIA, glucose monitoring, and calorie tracking. Clinical and biological data including genetics, metabolism, and gut microbiome are collected at baseline, every six months, and at study end over two years. The primary goal is to assess how biofeedback influences blood sugar and weight, with secondary insights into how commonly available biofeedback tools reflect underlying biology through multi-omics assessments.

Read More