Brand Refresh: Mascot

[mcturco]

In this issue, we will discuss concepts for an AsyncAPI mascot.

Currently, we have Eve & Chan (their names represent events and channels)

I think while the concept of them is cool, I feel that we need to simplify their illustrative details and perhaps create characters out of basic shapes (they will feel more like a flat graphical drawing with few curves and minimal shading/coloring)

Key Deliverables

Initial Sketches and Colour:

• [ ] Develop unique and simplified sketches for both Eve and Chan.

• [ ] Based on feedback and suggestions, refine 4 approved design concepts for Eve & Chan.

• [ ] Create a colour palette for Eve & Chan. This palette should be simple and adaptable, ensuring that the characters fit seamlessly into various environments or contexts.

Pose Variations:

• [ ] Develop 4 distinct pose variations for the Eve & Chan

Documentation:

• [ ] Document how the colour palette can be adjusted for different settings or branding needs while preserving the characters' core identity.

• [ ] Provide descriptions of the pose and environment variations, explaining the choices made and how they contribute to the versatility and usability of the characters in different settings.

---

References: The following references are to give us inspiration based on art style, not the actual character that is shown. We can use these drawings for inspiration to build the new look of Eve & Chan.

Reference 1: I enjoy the simple shapes and curves that this character has and the color palette is simple and adaptable for use in new environments.

Reference 2: Again, very simple shapes, colors, and facial expressions

Reference 3: These remind me a lot of Postman's "postmanaut", but I think we could potentially draw inspiration here from the body shape and translate that style to Eve & Chan fairly easily

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[WeeProducciones]

hi! this is our sketch of proposite for the mascot :), we design this mascot because we want to respect the first idea and use an alien. We think that is adorable, funny and very easy for put in all the elements of merchandising, but we want your feedback for continue working on this or think other idea if you don´t like. :)

[fmvilas]

@WeeProducciones I wonder if we can start a version without colors and just lines. Then add colors after we have a final candidate. And then put them in specific situations or placements once we have the mascot.

I specifically like the way Fido Dido was conceived. It's a simple figure but then 7UP put it in multiple places and situations. It's always recognizable, independently of the artwork.

[mcturco]

@fmvilas and I spoke about fido dido concepts in the past, and I started drawing some ideas for how Eve could look based on this art style. Here are my initial iterations, hopefully this helps!

[WeeProducciones]

Great, we can try these things that you tell us, fidodido is a pet that we love. the adaptation is great

[derberg]

I just wanted to jump in here to say I love the idea as it reminds me of times when I was young

just eyes in your proposal could get more in line with ☝🏼 or to be more alien I suggest look on eyes of goats and sheep 😄

[WeeProducciones]

yes, they have been our inspiration. now we are working on a new proposal more similar to Fido Did

[derberg]

oh, interesting, Fido Dido seems strange for a mascot. It is kinda "long", which is I think hard to print on stickers and other stuff as then you need to make it big to show details. I hope you know what I mean.

while you current approach based on The Powerpuff Girls is "short".

"long"/"short" -> I'm referring mainly to legs that in case of Fido Dido make the figure, the mascot long, high. I'm not sure how to express it better 😅 I've never seen "long" mascots in tech

[fmvilas]

What I meant proposing Fido Dido as an example is that it's easily recognizable, easy to adapt, etc. I didn't mean it has to be lines or it should look similar somehow. It's more about its traits than its appearance. I hope it clarifies things a bit.

[WeeProducciones]

Hello! Sorry for the delay, it being so difficult to find the rigth personality. This sketchs are our favorites, but are sketches yet. We think that they can be friends and appear toguether. what do you think about this?

[WeeProducciones]

the intention is to work the cloud ship and maybe work the extremities

[derberg]

some inspiration from https://chat.openai.com/

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/medium, bounty/design First assignment to regular contributors: 2024-09-20 00:00:00 UTC+12:00 End Of Life after: 2024-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[nwanduka]

@Mayaleeeee I'd like to work on this task for the Bounty Program. After reviewing the issue and the bounty rules, here's my proposed plan for approaching this project:

Research & Conceptualization (3-4 days)

• Carry out research on AsyncAPI's core concepts, values, and brand identity
• Analyze mascot designs from similar tech companies and open-source projects
• Brainstorm and sketch initial concepts for Chan and Eve, focusing on representing AsyncAPI's event-driven architecture theme

Initial Design (4-5 days)

• Develop 3-4 rough design concepts in Figma
• Ensure designs are scalable and work well at different sizes

Community Feedback (2-3 days)

• Present initial concepts to the AsyncAPI community for feedback
• Collect and analyze responses
• Identify the most promising direction based on community input

Refinement (3-4 days)

• Refine the chosen concept based on feedback
• Develop color variations and experiment with different styles
• Ensure the mascots work well together and individually

Final Design & Deliverables (5 days)

• Finalize the mascot designs in Figma
• Prepare different file formats as required (SVG, PNG, etc.)
• Document the design process and rationale

My proposed timeline fits within the required project duration, with a significant buffer. This is to make sure that I complete the task (including all iterations) in time. Throughout the process, I plan to provide regular updates in the GitHub issue and be responsive to feedback and direction from the maintainers.

I'm excited about the opportunity to contribute to AsyncAPI's visual identity with these mascot designs. Please let me know if you need any additional information or if you'd like me to elaborate on any part of this plan.

[miracle-E]

@Mayaleeeee Here's my project delivery breakdown

Phase 1: Research and Planning (2 days)

• Define the Mascot's Role:

  • What is the purpose of the mascot? Is it to represent the community, the technology, or both?
  • How will the mascot be used? In marketing materials, events, and online communities?
  • Generate various ideas based on AsyncAPI's core concepts (asynchronous communication, APIs, etc.)
  • Consider different visual styles (cartoonish, realistic, abstract) and personalities.

Deliverables:

• Brand exploration: Review AsyncAPI's mission, vision, values, and visual guidelines.
• Audience analysis: Identify the target audience, e.g., developers, businesses, or API users.
• Competitor analysis: Research other mascots in tech (e.g., Kubernetes’ Phippy, Docker’s whale) to understand best practices.
• Moodboard: Collect mascot references from various sources to identify potential styles, personalities, and characteristics.

Key Considerations: Who are the primary users of AsyncAPI? What are their interests, preferences, and humor?

Phase 2: Concept Ideation (4 - 6 days)

Objective: Brainstorm and sketch various mascot concepts. Deliverables:

• Sketches: Produce initial rough sketches of 2 different mascot concepts based on the ideation session.
• Character traits: Define the personality traits and story of each concept (e.g., friendly, geeky, playful).
• Initial feedback: Present the initial sketches to stakeholders for feedback on preferred concepts and incorporate feedback

Key Consideration: Consider factors such as memorability, versatility, and potential for merchandise or digital assets.

Phase 3: Feedback Objective: Share initial concepts with the AsyncAPI community for valuable feedback, gather and evaluate responses, and use community insights to pinpoint the most promising direction.

Phase 4: Mascot Development and Guidelines (6 - 8 days)

Develop Mascot Guidelines:

• Create a document outlining the mascot's personality, attributes, and usage guidelines.
• Specify appropriate color palettes, fonts, and design elements.

Create Digital Assets:

• Develop high-quality digital assets, including vector files, PNGs, and GIFs, for various applications (website, social media, merchandise).

Consider Merchandise and Branding:

• Explore opportunities for merchandise (t-shirts, stickers, mugs)

Phase 5: Testing and Feedback (3 - 4 days)

Gather Feedback:

• Share the final mascot design with the AsyncAPI community and stakeholders for feedback.
• Address any concerns or suggestions.
• Revise the design or guidelines based on feedback.

The timeline can be adjusted based on complexity, feedback loops, or additional rounds of refinement.

I have a rough draft of a possible concept here

Looking forward to bringing the AsyncAPI mascot to life.

[Oloso-surur]

@Mayaleeeee Here's how I will approach the redesign of Eve and Chan:

• Week 1 Research & Inspiration

First, I will dig into the references provided in the issue and really study their style. The goal is to simplify the mascots using basic shapes and a minimalistic approach, so I’d look at other flat design characters for inspiration—focusing on what works and how I can keep Eve and Chan recognizable while taking away unnecessary details.

• Week 2 Concept Development

Next, I will start sketching out different design ideas for both Eve and Chan. These concepts would explore different ways to simplify them using simple shapes like circles, rectangles, and minimal curves while still keeping their personalities intact.

• Week 3 Feedback Loop

Once the initial designs are ready, I will share them with you and the feedback. This step is very important, as I want to make sure that the designs resonate with our brand guidelines.

• Week 4 Refinement

After gathering feedback, I will go back and refine the designs, incorporating the ideas and suggestions. My goal would be to finalize a clean design for each character.

• Week 5 Documentation Lastly, I will wrap everything up with documentation to explain my thought process, how the feedback influenced the designs, and why I made certain choices in terms of shapes, colours, and style.

Thank you.

[Mayaleeeee]

Hey @miracle-E @Oloso-surur

Thanks so much for showing interest in the design bounty! I appreciate all of you taking the time to check it out.

I will move forward with @nwanduka since she was the first to jump in with her approach.

That said, I’ll keep you in mind for future design opportunities.

Thanks again for your enthusiasm! 😊😊

cc @aeworxet

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2024-09-24	2024-10-07	2024-11-17	2024-10-20	2024-11-03	2024-11-17

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[Mayaleeeee]

Hey @nwanduka, I hope you're doing well! How is the task progressing? Are you encountering any challenges, or is there anything you'd like help with?

Also, please share your weekly updates here so we can stay on track and ensure visibility.

Thanks, and let me know if you need anything! 😊

[nwanduka]

Hi @Mayaleeeee. Thanks for checking in. I'm doing great. The task is progressing well. I made a few hand sketches yesterday. Should have a draft design ready soon so I can get feedback on them. I won't hesitate to reach out if I need any help. Thanks again

[nwanduka]

Hi @Mayaleeeee, here are some ideas I sketched for Chan and Eve. So while working on these, I tried to to address the feedback that have been previously provided in this discussion.

Here are key design considerations I made in the process:

• As @mcturco requested, I've simplified the illustrative details, using basic shapes and minimal curves to create more versatile, flat graphical drawings. I've used very limited shading, mainly to define essential features like eyes, keeping the designs flat and easily reproducible.
• The designs are presented in grayscale, focusing on the line work and shapes. This allows us to evaluate the core design before adding color, as suggested by @fmvilas.
• Distinctive personalities:
  • Chan (Options A & B): I've explored two directions – a cute, approachable bunny-like character and a more robotic design with large, expressive eyes reminiscent of the Power Puff Girls style mentioned by @derberg.
  • Eve (Options C & D): Option C has a flame-like hair element to symbolize energy and innovation, while option D incorporates a visor-like feature for a tech-savvy look.

I'd like to get your (everyone tagged) thoughts on these concepts and which ones we feel best represent AsyncAPI.