Learn more about our products:
-
HTML5, Unity iOS/Android, Mac, Windows/Xbox
Augmented/virtual realities
Game design, creative concepts, UX/UI design
Rapid prototyping
Hardware integration
-
2D and 3D animation
Conceptual design
Characters and environments
Storyboarding and layout
Scriptwriting
Sound design and production
Visual effects and post-production
-
Original IP creation, development, production
Creation, development, production of long and short-form broadcast content
Head writing, show running, executive producing
Click here to see our moonladder page
-
Audio strategy and podcast concept development
Extension of existing properties and new IP development
Executive producing, show development, writing, directing
Click here to see our audiyo-yo page
-
HTML5, Squarespace, Wordpress, Drupal, and custom CMS
UX/UI design
Visual design and production
-
Extend properties to multiple platforms
Content integration
Branding and messaging
Product definition
Process & Approach
We pride ourselves on a collaborative process with our clients. Both teams work closely together during all phases of the project—from brainstorming and design through production and launch.
We use an iterative process throughout production. While every project and every partnership is unique, here are some of our best practices:
Joint working sessions
Joint working sessions (in-person or virtual), especially at the beginning of the process, can help establish a “sleeves rolled up” dynamic that carries throughout development. We like having input and making recommendations for design tweaks that will enhance the experience, and implementing if all partners are in agreement.
Establishing a shared vision and vocabulary
This process works most effectively when there is a shared vision, and open dialogue between teams. It’s critical that from the very beginning, we establish a shared vocabulary and set expectations for turnaround times, feedback, and deliverables. It may sound obvious, but we all need to agree on what we are building, who we’re building it for, and what we expect/hope it will do.
Building small components to test early
This is the best way to minimize impact on schedule and budget, and ensure the best possible experience for the end user. Early planning lays a foundation for the rest of the project. If we collectively agree that significant changes are needed, we problem-solve as a group to find solutions, and discuss any impact on deliverables.