About DevConsole
The DevConsole for JioImmerse is the Admin Dashboard for creators publishing to the JioImmerse ecosystem, be it for VR apps for JioDive - Jio's Mobile VR ecosystem or for JioGlass - JioTesseract's flagship enterprise smartglasses and for all future devices created for the JioImmerse ecosystem.
About Developer Program
Under a Developer Program, Jio em-panelled more than 60 developer teams to create Mixed Reality apps. These apps will be published and distributed through an app store. The DevGrowth team is currently in charge of managing interactions between developers and Tesseract, but with more and more developers registering every month, the manual operation has become unsustainable.
The need for a developer dashboard has arisen to automate and streamline these processes, provide real-time insights and analytics and improve the overall developer experience.
The Challenge
JioImmerse's developer program had quickly outgrown its manual processes. With over 60 developer teams creating Mixed Reality applications for platforms like JioDive (mobile VR) and JioGlass (enterprise smartglasses), the DevGrowth team faced significant operational bottlenecks:
Manual developer onboarding requiring extensive documentation and communication
Fragmented collaboration across Google Drive, email, and spreadsheets
Time-intensive testing and approval workflows managed through multiple touchpoints
Limited visibility into application performance and developer progress
These challenges were preventing the DevGrowth team from focusing on their primary mission: growing and nurturing the developer community.
My Design Process
1. Discovery & Research
I began by mapping the existing developer journey to identify pain points and opportunities. Through interviews with:
8 external developers
4 DevGrowth team members
3 QA specialists
Key Insights:
Developers spent a considerable amount of their time on administrative tasks rather than development
The DevGrowth team managed an average of 30+ email threads per project
Build approval typically took 2-3 weeks, with 80% of that time spent in communication loops
2. Problem Definition
I framed three core problems to solve:
How might we automate and streamline developer onboarding, approvals, and publishing processes?
How might we provide real-time insights to improve developer experience and app store success?
How can we enable the DevGrowth team to focus on strategic community building?
Key user personas
The console was planned to accommodate three key user personas:
For Developers:
Self-service team management
Project lifecycle tracking and management
Build submission and approval monitoring
Analytics and performance visibility
For DevGrowth Team:
Developer onboarding automation
Project approval workflow management
Community-wide analytics
For QA Specialists:
Streamlined build access
Structured feedback mechanisms
Testing status tracking
User Journey Flow
Since Developers would be primary users of DevConsole, their user flows were prioritised. It was decided that DevConsole has to cater to the developers first and foremost. So I mapped out an ideal user flow of all developer activities.
Once I had a high level user flow in place, I could move on to building the Information architecture. This user flow ended up informing a lot of components of the IA.
Information Architecture
In a project like this, we are dealing with multiple types of users and use cases. I always begin a project by first creating and getting consensus on an Information Architecture(IA) from the team. For me, IA is important in identifying and defining the relationships between different pieces of information, and it can help to identify any potential issues or gaps in the data that need to be addressed. This will help me to ensure that the DevConsole is effective and efficient in meeting the needs of the users.
Sketches
Wireframes
Style Guide
I whipped up a quick style guide, following the brand’s identity which was at the time, still a work in progress, but we couldn't afford to delay the launch of the Devconsole and sticking to what developers preferred the most: dark mode. Not gonna lie, a big reason we went with it is because it looks pretty awesome. Plus, it aligns with the current industry trend for developer tools, making it easier for developers to work in low-light environments. It’s a win-win if you ask me! 🙌
High Fidelity Designs
I created a high-fidelity prototype using the established style guide. These designs were specifically aimed at getting early feedback from stakeholders and the developer community. While feature detailing was still ongoing, the prototype focused on the areas where we had the most clarity, such as the sign-up/sign-in process, project creation, and app publishing. This approach helped us to validate the design concepts quickly and make iterative improvements.
Feedbacks and changes
We shared our high-fidelity designs on the Tesseract Discord server, a hub for developers building apps with our tools. The response was incredible! The prototype really brought the project to life for everyone, from our team to stakeholders, and helped us pinpoint some key areas for improvement.
The feedback sparked a flood of new ideas and user stories, and we dove right in, adding new features and refining existing ones based on the community's insights. It was amazing to see how engaged everyone was, and it solidified our commitment to building something they'll genuinely love.
Following that valuable community feedback, I decided to take a closer look and refine the design even further. I'm really glad I did! I noticed a few things that needed tweaking and made some quick touch-ups. It's definitely feeling much more polished now, and I'm confident we're ready to move forward with development, armed with both community enthusiasm and a refined vision
Revised Designs
Welcome page:
Sign-in / Sign-up elements:
Welcome screens:
Navigation (Side panel):
DevConsole - Home:
New Project Creation:
Project Overview:
App overview:
App Release Management:
App Performance and Analytics:
Team Members & Org Management:
Live Demo
Impact
Streamlined Processes
Faster and more frequent testing:
The DevConsole allowed developers to easily install and test their apps, reducing the time and effort required for sideloading.
Elimination of version errors:
With the DevConsole, developers could easily check and confirm the version of their apps before testing, minimizing confusion and wasted time.
Up-to-date APIs and SDKs:
The DevConsole provided developers with the latest APIs and SDKs, ensuring they were using the most current and supported versions for their apps.
Improved Developer Experience
Consistent and streamlined workflow:
We designed the platform to have a consistent and intuitive experience, reducing the learning curve for developers.
Release with confidence:
Developers can now manage and edit their app listings in real-time, improving discoverability and making a strong first impression on users.
Access to rich data and analytics:
DevConsole provides developers with in-depth insights into app performance, allowing them to make informed decisions and optimize growth.
DevGrowth and Tesseract
Improvement in team performance:
By not constantly catering to individual developers, the team was able to focus on onboarding 20% more new developers in a quarter.
Better app promotions:
The use of Tesseract allows for better targeted promotion of apps based on categorization and content ratings.
Understanding customer trends:
Dashboards such as DevConsole make it easy for businesses to understand customer trends, which enables better planning and packaging of services.
Faster approvals and feedback:
Streamlined communication has led to quicker feedback, encouraging more accurate iteration by developers. This in turn has led to better apps, improving the overall quality of the app store and ecosystem.
Learnings
Understanding the software development pipeline:
I gained insight into the inner workings of the operations that go into publishing an app, and maintaining it in a marketplace. Thinking from a perspective similar to how Google runs the Android Playstore pipeline and how iOS manages their apps on iOS app store.
Empathizing with multiple personas:
I learned to understand and empathize with different types of users, and to design pages with different requirements and limitations for each role.
B2B vs B2C thinking:
I learned that designing a B2B solution requires a different mindset compared to a B2C solution. B2B solutions are often tools that other people will use for their own benefit, rather than a product that users consume.
Project Update⚡
DevConsole is a live platform released in the summer of 2022. It is being used by more than 120 teams on a daily basis. About 200 apps have been published on JioImmerse App using the DevConsole. More features for analytics, monetisation and legal had been added since.
Thank you for reading
