I Bet I Could *Hook* You Into Redux Again Starting on a new project that uses React as a front-end framework with Redux, I didn’t know what to expect. Coming from native iOS development, handling state was relatively straightforward: if you made the decision to maintain a global application state, you created a locked-down singleton class with static methods to call throughout the app, and you’re done! Little did I know that for web development in vanilla React, with its virtual DOM and re-rendering, the application state had to be passed up and down component trees as props. Enter Redux: a platform-agnostic
On September 20, we gathered for our second annual LabsCon! Our one-day team member conference is stacked with talks where we teach and learn from each other. It was a jam-packed day at Detroit’s Jam Handy event space, with nine speakers delivering 30-minute presentations on topics that ranged from how training a dog can help a human learn new tricks to addressing anti-black racism and improving diversity and inclusion. How did LabsCon come to be, you ask? It was an idea that had been floating around for a few years, and last year we made the dream a reality. As a
Apple released the Xcode 11 GM, meaning that it’s now time to create our builds using the iOS 13 SDK and submit to the App Store! Here's an updated way to fix your simulator status bars for App Store screenshots with Xcode 11 and iOS 13.
By Karen Ford While recently working on a project that relies heavily on Charles Proxy to run multiple parts of our web app, there was a need to test on a variety of devices that our developers and QA team may not have access to (*cough* Internet Explorer *cough*). Our team went ahead and set up accounts for BrowserStack, but realized that we wouldn’t have a way to utilize Charles while using the out-of-the-box BrowserStack. This was a problem, as many of the scenarios that needed to be tested could only be done through Charles. After a bit of searching through BrowserStack’s
By Katrina Ohlemacher Douglas Adams once said, “Writing is easy. You only need to stare at a piece of blank paper until a drop of blood forms on your forehead.” While it’s true that it can be difficult to transfer thoughts from your brain to the page (see the photo above - those are real stickies on my monitor right now), I’ve found that my history as a writer and editor provides some unexpected benefits when it comes to software testing. Some people are visual thinkers, and some people are verbal thinkers. I’ve always been a writer and verbal/narrative thinker. I don’t
Originally posted on Ford Website by Drew Kidd Kim Sfreddo faced a daunting task one afternoon while flipping through a stack of résumés looking to find a new software engineer. “You invest a lot of time and energy going through résumés, interviewing and on-boarding applicants just to see they’re not working out after a few months,” said Sfreddo. “Then you have to start all over again, and in this fast-paced environment, we need to deliver.” That’s when Sfreddo, a mobility platforms and products connected vehicles supervisor, realized her team needed a different solution if they were going to be agile enough to create
by Aisha Blake This post was originally featured on Aisha's blog A coworker recently came to me for advice on attending his first conference. He was about to leave for Google I/O (he thinks big!) and wasn’t sure how to make the most of it. I answered off the top of my head at the time but it got me thinking about what makes for the best conference experience. I hope you’ll find these tips useful! The plan is to build out future posts based on many of the topics I touch on here. If there’s anything in particular that you’d like me
On this episode of Labs Live!, Dan and Tobi welcome Lauren Mathieson, Senior Product Designer at Detroit Labs. Tune in to watch them discuss UX Research and its role in the product development process.
While in the midst of building, we realized that one of the requirements for deploying was to have certain URLs/keys/secrets be pulled from Docker UCP and dynamically defined without having to rebuild the entire single-page app. Ultimately, we came up with a solution that doesn’t use a back-end and still lets us create dynamic environment variables. Here it is in four simple steps.
Have you ever worked on a project that didn’t have any defined requirements when you started on it? And even after requirements were initially determined, they continually changed? And after you’d build a feature, it would get removed, and you’d have to get rid of your work? As much fun as this sounds (read: not at all), it can be very challenging to be on a project like this. Morale suffers, as do any feelings of accomplishment. It can also be challenging to know where to start on these ill-defined projects. Here are some suggestions for making it through.