For those of my readers who had been following along (or, for those who had read and skimmed through my older posts), a classic and cute, humorous article from January 2019 comes to mind, as the year ends, and that progress ought to be made on the development aspirations that had come to light, as I traversed about Downtown Los Angeles, keeping with the spirit of that I could help keep the pigeons well fed, throughout the seasons.
Here’s the gist of the article, which was a photo blog.
This morning, within the space of about an hour or so, I was able to finish off a rendition of a logo I’d been recently tasked with, as for my Google Developer’s aspirations (here, in the workload laid in front of me of needing to create a logo for Google Pay Passes - a splash screen that the user would encounter that would include some terms and conditions, a privacy policy, as well as information of my company, iPigeon.institute, for the sake of the purchaser, or for the sender of finances for my company, or, in the case that I’d been planning on, a recipient of a QR code that would enable the user to gain special access to retail or gift card | loyalty goods, or rewards, for happening upon my marketing material in the form of the IoT object: the QR code [which needs to be decoded, that it must properly trace back to the website that I’d like the client to discover, through Google Lens]).
Here are some of the objects that I rendered out for the compositional logo
 |
| My final and first rendition of a feasible mockup of a nicely-composed logo, based on guidelines with well-written instructions (thanks to Google), and it came out nicely! - I’d say, for a first run. I’ll update later on as I fine-tune the logo and it’s coloring and detail features. |
 |
| Creating a logo of appropriate technical considerations becomes a tantamount priority for the conscientious developer. End users could ostensibly be quite picky about the sort of aesthetics they allow in to their device and user interactions. I created this guide for my scratch first copy logo based on the Branding Guidelines page for Google Pay Passes Application Programming Interface Developers-in-the-making (documentation). |
 |
| Some of the composite elements that went in to the logo. |
 |
| Adobe provides fine tools and licensed ( - for particular use case scenarios) fonts that can be integrated in to a new creation in their fonts for developers site. Here, I used Adobe Caslon, designed by Carol Twombly. Thanks, Carol! A finely rendered classically-styled font. |
The impetus for creating this design comes from Google’s Pay Passes standards, which lay out the guidelines for brands creating a pay portal for payments, loyalty cards, and barcode redeemables.
Since yesterday morning, here’s the progress I made in developing for this proportion and frame size composition. I decided to make it a Christmas 🎄theme, in the spirit of the holidays, and to set myself about a goal of attaining a Pay Passes API QR | barcode-scanned redeemable marketing effort outreach and engagement with my blog’s content and purpose.
 |
| Some more imagination towards the design of the logo imagery, after a day spent researching and establishing other project metric gains in creating Google Pay Passes. |
Here’s a clip of the design development process, as I implemented it, based on Google’s Logo colorings, posted on YouTube.
