feat(example): update app icons

[Gustl22]

Description

I created a logo for our library (or mostly for the exapmle app) in style of the Flutter logo. Idk if you more want sth that matches the Flame logo. E.g. a burning note (?).
Or we can change it again, if we crave for sth better :)

Checklist

• The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs:, chore: etc).
• I have read the Contributor Guide and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
• I have updated/added relevant examples in example.

Breaking Change

• Yes, this is a breaking change.
• No, this is not a breaking change.

Related Issues

[spydon]

Woooow, looks great!
I don't think it has to look like Flame since it is completely separate from flame. :)

[erickzanardo]

Love it! You should put it on the readme too :D

[spydon]

Love it! You should put it on the readme too :D

Agree! Maybe in a similar fashion like we do with the centered Flame logo? 😍

[renancaraujo]

Love it!

[Gustl22]

Unfortunately CSS styling is not a thing in GH, so I have to add the text in the logo itself. I tried many combinations, and as the name is that long, it looks weird to put it under the icon, so I put it next to it like done on Flutter itself.
You can preview README here, as the link to the logo is not yet existant (only after merging) to provide absolute paths due to the monorepos subpackages.

Compact	Horizontal	Vertical

[spydon]

Unfortunately CSS styling is not a thing in GH, so I have to add the text in the logo itself. I tried many combinations, and as the name is that long, it looks weird to put it under the icon, so I put it next to it like done on Flutter itself. You can preview README here, as the link to the logo is not yet existant (only after merging) to provide absolute paths due to the monorepos subpackages.

Nice, the first one is my favourite!
Make sure to store both the logo separately and the logo with text in the repo so that we can use them as fitting in different contexts.

[erickzanardo]

First one is my favorite as well!

[Gustl22]

For me personally or from Design perspective I think the second variant is best for the README header as it states the package name more clearly and possibly bringing less confusion to the users.
But I'm also happy to change it to the first variant! Won't make much of a difference in the end. I can add the other ones as well for completeness. I always provide vector files, which can be manipulated as desired.

Only for clearing the terms:
icon - the icon / brand itself
logo - the brand mostly with text

[Gustl22]

Changed to compact logo. Looks quite clear too :)

[luanpotter]

OMG this is so awesome