We all have at least one framework/technology we love and try hard to keep up with. The one we read never ending blog posts on. The one we use on our side projects. For me that has been Spring boot for a while now.
Wellbeing We’d hoped Google would talk about their Digital Wellbeing features at Google I/O 2019. They took some good steps forward in helping implement technologies to curb cell phone addiction. (More about what we had hoped to see on our predictions blog.) We really liked the thoughtfulness behind this initiative. More OS focus on digital wellbeing will place more user scrutiny on app behaviors. It's more important than ever to find the right balance between data that is necessary for apps to help empower the user vs. data that is interesting/valuable to the company collecting it. We love this push forward in the mobile
Google IO is almost here and we’re all counting down the days until we can get our new *fingers crossed* Google Pixel. We asked some of our Android devs what they are hoping to see announced this week. So here it goes: Detroit Labs developers’ quick take on their predictions, hopes, and dreams for Google IO. New/Cheaper Pixel Phones We’re excited about this one because of our wallets, but also because it’s a major indication of Google’s return to the mid-range market. Don’t get us wrong, we want the flashy/high-tech phones too, but we don’t want anybody to be priced out of
As an organization, you are always looking for ways to innovate and bring new ideas to market fast. But the desire to move quickly can often lead to wasted time and money. So, how do you act decisively while keeping up with the rapid pace of technology? Consider investing in building a Proof of Technology. It’s a surefire way to validate (or invalidate) your most ambitious technology-based ideas. If the technology landscape is holding you back, consider these four benefits to building a proof of technology to help you move forward. 1. You invest a little and learn a lot Funding a
As Talent Specialist at Detroit Labs, specifically for our OnSite team, I've seen a lot of resumes. While our team who works out of 1520 Woodward (we call them our Services Team) uses a GTKY and not a resume as a main point of reference, we work with our clients and use resumes as a point of reference. If you’re one of those people who updates your resume constantly, that’s amazing. You should be proud! For the rest of us, revamping our resume only happens when something annoying happens at work or if we unexpectedly lose a position. Many of us
By Stuart Kent Recently, Terry shared his secrets for creating a successful proof of technology --Today, I’ll explain how our eight-week Proof of Technology engagements are structured to support that exploratory process and allow us to consistently provide valuable results. Week 1: Kickoff & Problem Definition Each engagement begins with a kickoff meeting where all team members are introduced and lines of communication are established. Since Proof of Technology engagements inevitably involve branching explorations and dead ends, it is especially important that we identify a product owner on the client side who is empowered to quickly make decisions and provide feedback. This meeting
When it comes to building out a proof of concept (we call them Proof of Technology), the first thing we need is an idea. Your idea. That thought that started as just a spark and has now consumed you. What is it? How do you envision it working? If possible, how does it change your company, your industry, your users’ experience? An idea can be difficult to communicate, which makes it hard to get the buy-in you need to move forward. Depending on your company culture and structure, “innovation” gets more and more challenging as your business matures, because time-tested, predictable