This is a three part post about my experience using AWS Amplify to develop a food logging app for the Metal Toad hackathon. In part one I covered the initial project overview/setup and our experience implementing Amplify Auth. Here in part two I will cover Amplify Storage. Finally, part three will cover my favorite part, Amplify AppSync and PubSub.
This is a three part post about our experience using AWS Amplify to develop a food logging app for the Metal Toad hackathon. Here in part one we cover the initial project overview/setup and our experience implementing Amplify Auth. Part two will cover Amplify Storage, with part three covering Amplify AppSync and PubSub.
I’m used to thinking of ergonomics in terms of chairs, desks, physical plant, tennis rackets, etc., but this week our expert UX designer, Cami, blew my mind when she shared a “natural thumb extension” image that she uses to help design for mobile.
“What’s this?” I asked
“The green zone is where the controls should be,” she replied.
“Ohhhh,” I said. “Ahhhh….”
After years of building and publishing on them, I'd love to say I knew CMS frameworks like Drupal and WordPress would be this huge. In truth they got this popular because of their great open-source communities; both of which I'm trying to participate and contribute to more. Why? Because closed platforms like SquareSpace and Adobe's content platform are rushing ahead without having to worry about backward compatibility like WordPress and Drupal does. These newer, closed systems insulate users from the backend and abstract away many of the same complexities WordPress.org and WordPress.com solved. They can push forward faster with newer, cleaner, “from-scratch” user-experiences because they don't need to maintain compatibility like "the big PHP" CMS's.
Anyone who has delivered a Drupal site to a client knows that the user interface does not always receive a warm reception. As Drupal geeks we have grown accustomed to the admin interface and workflow of creating and managing content. However, for many clients Drupal is uncharted territory and the user experience can be one of confusion and fear (‘you’re not in Facebook anymore!’)
Over the years, I've created a list of ways to make Drupal easier for one of my target audiences: the non-technical admins and editors that run the day-to-day operations of a website. My list is getting huge, but the following six ideas are always reliable.
It used to be that cars were simple. If your car broke down, a guy could pop the hood, check a few wires, hit things with a hammer and actually get things to go again. Modern car engines have come a long way, and now are a complex system of 500+ components. Gone are the days of carburetors. Now we have fuel injectors.
We're just getting back from a great weekend at DrupalCampLA. A lot of topics were raised there but the message that really came home for me was this: as Drupal service providers we have to get CMS administrators to fall in love with Drupal.
Do your clients love you with such a furious passion that it borders on problematic? Do you find new customers calling you and saying things like, "I must have your services! My friend has been bugging me all week to call you. Seriously, I just want him to stop camping out on my lawn. It's scaring the children."
It seems that I hear a lot of people within the Drupal community focusing on how to make Drupal scalable. This is all well and good, but Drupal does scale; the Emmys know this, the Grammys know this and so does the Economist. Drupal can handle millions of page views in single day and frankly this isn't an issue that most websites face.