Insights about the app design and development ecosystem.
Murilo CamargosPosted on Django built-in migrations were designed as a way of propagating the changes you make on the models to the database. Migrations exist mostly to keep your code in sync with your schema and to provide a good way of versioning it. We just need a couple of commands to get our apps up and running with an updated version of our database, or not.
Rodrigo LanderdahlPosted on First, let me get this out of the way: this is not a Django vs Phoenix post. We at Cheesecake Labs believe polyglotism is good; it gives us options. Since the beginning, we’ve mostly been a Django shop for backend services and will continue to be for many years to come. It is a stable, fully-fledged and widely adopted framework that’s used to power a shocking amount of large applications, including many client projects that we’ve developed over the years.
Angela MansimPosted on “Branding is what people say about you when you’re not in the room.”
So how about having a seat and staying in the room? To have a seat nowadays, a brand should have feelings and opinions, not just sell itself. Otherwise, it will have to leave the room. That’s what we call Branding Experience.
NicholasPosted on I have a Komeco air conditioner in my bedroom. It is controlled by an IR remote controller (ZH/JT-03) and, as a home automation hobbyist, I really like to control my home appliances with my Watch, Phone, Google assistant, Alexa, etc. You got my drill. In simple words, I’m lazy, thus I try to automate everything I can.
Danilo WoznicaPosted on How one methodology allowed me to create a great design system from scratch and made me a better developer, with principles of componentization, hierarchies and reuses of code.
Francieli LimaPosted on Since I started building apps I was sure of only two things: one is that I love seeing users enjoying my apps; and the second is that I hate seeing users clicking everywhere and crashing them. So how can I be sure that my users will be able to have a joyful experience (even with those features that are hidden 15 clicks away and that I don’t even remember they exist anymore)? By testing them all!
Alex CordeiroPosted on Cheesecake Labs is very excited to be featured in Clutch’s latest announcement of its Top Latin American Developers & Agencies 2017, which recognizes the leading regional technology development, marketing, design, and related digital services companies with excellent client satisfaction.
Ricardo Gehrke FilhoPosted on Integrating apps and servers is not an easy task, we all know that. Even with great tools like Alamofire and Retrofit there are still a lot of things to take care of in the app side: different endpoints, encoding / decoding JSON strings, API versions, data consistency and so on…
Recently I have worked in a project with server integration and we had the opportunity to choose new technologies to work with and to try to avoid some of these problems. The choice was a GraphQL server and in the app side the Apollo framework.
Rodrigo LanderdahlPosted on In the last few months, I worked on two projects that were similar in scope and complexity; both were API backends for mobile apps, had similar requirements and timeframes. However, one thing set them apart: one was written in Django + REST while the other was written in Clojure + GraphQL.
Since I was the main developer for both projects, I was able to make useful comparisons between both approaches. In this post, I’ll describe the pros and cons of each.
Ricardo Gehrke FilhoPosted on To use or not to use Xcode’s Interface Builder (let’s call it IB) is a very common discussion between iOS developers. There are many arguments against using it like version control issues and difficulties in debugging. This post in our blog have some considerations about it for example. But I believe that if the project is well structured and the team knows how to use it, these issues can be avoided and IB can become a very powerful tool.
