The process of adding Easter eggs inside projects is about creating informal inside jokes very well hidden, which aren’t usually revealed to clients or users. Most often, those do find about them by themselves after doing unexpected actions on the application, such as going through fake walls, series of key presses, opening the application at a specific location and/or time, etc.
Many companies, even the biggest ones out there, have been implementing Easter eggs in their products. One of the latest examples of this is Google’s Easter egg at the release of the Marvel Studio’s Avengers: End Game. Upon searching for Thanos and clicking on the glove, a script will run and automate the destruction of most of the web page, as shown on the video below.[av_video src=’https://www.youtube.com/watch?v=BBfbu-HfkOk’ mobile_image=” attachment=” attachment_size=” format=’16-9′ width=’16’ height=’9′ conditional_play=” av_uid=’av-9dys9′ custom_class=”]
Why are they so important?
Even before getting released, those have a clear impact on development. Towards the end of development, employees are usually feeling burned out, in need of both sleep and laughter. Easter eggs easily help brightening the mood of the office, since those are often created out of jokes or silly ideas which grew out of proportion.
After release, they usually are a fun way to tease your users and clients, depending on the type of person you have in front of you. Telling them “there’s an Easter egg in the app, have you found it yet?” make them curious and most often will get them to search the application and use it a lot more often. Additionally, asking your client to add an Easter egg themselves is something we would recommend. For instance, on a project we’ve worked in the past had put their initials on their main 3D model on the production build. Later, they could ask their users whether they’ve found it or not and have it as a joke.
Lastly, years after developing the project, rediscovering them is one of the best feeling. Easter eggs usually creates a lot of memories and good times, and often are associated with the core of the project while being a very discrete and pointless feature.
Example of Easter eggs
One of our developers really likes secrets and Easter eggs in general, and secretly stuffs every project with those without telling the rest of the team. While a lot of trust must be involved in this process, depending on the culture of your work environment, those can be well received.
One example of something they did, was to add one of their character inside a secret room in one of our demos and removed the collider on the wall so you can walk right past through it. That kind of harmless detail can easily make somebody’s day.
Another example is adding additional needless information in the repository commits descriptions. It’s important to ensure that all the commit information is self-explanatory and accurate but adding a little weird sentence here and there can’t do any harm (unless the repository is meant to be transferred to the client).
Sample from one of our repositories commit list.
A very common type of in-company Easter egg is the misuse of code comments. While most of the comments are either formal and useful, some may include screams of agony or just plain weird content. Those are usually picked up during project review or project de-dusting, and often catches developers off- guard. A silly example of this type is this type of comment.
One of our developer hates series of clothing curvy brackets.
In short, based on the type of culture present in your company and the context of the current project, there is no reason why you shouldn’t add Easter eggs here and there. Do keep in mind that those should remain harmless for the sake of staying a joke rather than becoming a source of problem or arguments.
Have a wonderful day!