Gambit
Intro
The project arose from observation in our team. We saw the difference in tools between designers and developers, which translates directly into the quality and time of work and understanding how the web works. We decided to solve this problem by creating a web editor based on the interface of graphic programs.
Background
About
Gambit is BIM for web development. It aims to solve the designer-developer conflict by providing a cohesive set of independent tools tailored specifically to each project's role.
What is BIM? Building Information modeling is an intelligent, model-based process that provides insight for creating and managing building and infrastructure projects faster, more economically, and with less environmental impact.
Core info
Team size
End users
• Web developers
• Digital agencies
• Startups
• Teams
Role
• Product Designer
• UI Designer
• UX Designer
• Animator
Business requirements
• Identify pain points in the existing workflow and propose a new approach
• Establish revenue model
Tasks
• Define a business model
• Establish a marketing strategy
• Market research
• Establish MVP
• Interviews with potential end-users
• Collect feature requirements
Market
EHS
Environment Health and Safety
Since 2013 delivered, implemented and developed till now
Study

Editor wireframes | 2016
Project data
Project challenges
• Design no-code tool for creators
• Define all cross interactions in the development team
• Define and design all supporting applications
• Keep consistency across all apps
Competitors
• Wix
• Webflow
Resources / Knowledge base
• Material Design
• Apple Human Interface Guidelines
• Youtube
• Smashing Magazine
• Medium
Used tools
• Adobe Photoshop
• Adobe Illustrator
• Adobe After Effects

Gambit page editor concept | 2016
Gambit Workflow promo movie| 2016

Research
- There are no tools for web designers and for cooperation with programmers
- Large market but not well developed
- Lack of understanding of web design
- Editors on the market require coding knowledge or were too trivial
- Page Editors usually don't were adapted to RWD
- Market solutions did not support CMSs
- Despite the known solutions with development tools, editors, none of the parties doesn't have a version control
- The only solution that partially matched the idea was from a different industry

Pain points
- Creation of the platform architecture
- Lack of good practice from the market, which could shape the project
- Small team
- The complexity of the project was difficult for the recipient to understand, and the analogies used trivialized the problem that could be solved

Work with all kinds of content 3
From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.



Features


Deliverables
- MVP
- Unified design systems for the platform
- Tons of editor prototypes
- Promo movie (my first and list after effects project)
- Market and competition analysis
- User interviews

Results
- MVP has been on implementing our business partner from a group of Fortune 500.
- Work on Gambit resulted in the creation of a framework that will be used in future projects.

Work with all kinds of content 3
From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.From colors to images, text to numbers, define the content and structures you need for your project.



Summary
Despite the extraordinary commitment and hundreds of hours of work on the board, notebooks, code editors, and graphic editors, we managed to create a residual prototype of the application. We tested the resulting components on some websites that we were implementing at that time as a team of freelancers. The project turned out to be too big for such a small group, but we did not give up on the need for such a tool and changed our work approach.
From the set of many modules that constituted the platform, we distinguished the key ones to extract those that have a chance of the fastest monetization. We've done what's known in startup manuals as a pivot to keep going on our big project.