Insights about the app design and development ecosystem.
Daniel LeitePosted on When we think about the process of developing an MVP, what we have in mind is to create great value in a short period of time, avoiding complexities and solving problems in the simplest way possible.
Then, on a beautiful sunny summer day, the Project Manager comes up and says:
“We need to create an MVP for a chat system in just one month!”
Marcelo GraciettiPosted on The dev team at Cheesecake Labs has been using VIPER for iOS and Android mobile app development for over one year and we just love this clean architecture!
This article summarizes our best practices on the VIPER architecture, using code examples from our VIPER boilerplate. The code samples used here are in Swift, but all concepts mentioned may be applied to an Android project developed with VIPER, either using Java or Kotlin.
Thiago VictorinoPosted on Building a product is no easy task. It’ll take months of planning, design and engineering work, but with dedication, hard work and the right professionals by your side, it can be accomplished. However, how can you know if you’re building the right product? Dedication and hard work alone won’t be enough. There’s another factor to consider on the equation: if it solves a real problem for real people. Many startups often decide to go straight to the building phase and end up missing some important steps of the product development process, such as validating their business idea with potential customers and analysing the market. Let’s go over some things to take into account when setting a product strategy.
Andrio FrizonPosted on When we start the development of a product, there is always a desire to make it as perfect as possible: fulfilling client’s expectations, offering a good learning opportunity to the developer and delivering a system with high maintainability and scalability.
As the code base grows, keeping it problem-free becomes a harder challenge. Testing manually each module of the application can take so much time that developers may become unproductive.
Marcio Granzotto RodriguesPosted on Starting as an Android developer and later working with iOS as well, I had contact with several different projects’ architectures – some good and some bad.
I was happily using the MVP architecture for Android until I met – and worked eight months with – the VIPER architecture in an iOS project. When I came back to Android, I decided to adapt and implement VIPER on it, despite some other devs suggesting it wouldn’t make sense to use an iOS architecture on Android. Given the fundamental difference between Android and iOS’ frameworks, I had some questions about how useful would VIPER be for Android. Would it be doable and worth the effort? Let’s start with the basics.
Clarice BianchiniPosted on Think of a professional who has changed the history of IT for a second. If the person who came to your mind was Steve Jobs, Bill Gates or any other male name, it’s no wonder. Although the history of computing is marked by contributions from great women, such as Ada Lovelace, Grace Hopper, Sister Mary Kenneth Keller and Hedy Lamarr, women are still seen as if they played a secondary role in this market.
Daniel LeitePosted on As a JavaScript developer, we should know that most things are objects – from core features, like strings and arrays, to the browser’s APIs. Here you can have a full introduction about objects in JavaScript.
JS’s objects are so beautiful: we can copy them, change and remove properties and do many cool things.
Silvia MedeirosPosted on If you are not considering the user experience when designing a new mobile application, it’s time to start thinking about it. One of the most important things to have in mind when you design a mobile app is making sure that it is useful and intuitive for the users. If it’s not useful, it won’t have a practical value. At the same time, if the application is useful, but it takes too much time and effort to be used, people won’t engage with it.
Hannane CherifiPosted on Defining the personas that represent the audience of a product is a very important step of the design process. There are many methods out there to help us figure them out. But the question is: do we empathize with them the way we should?
Continue Reading
Jonatas BaldinPosted on As a software developer, I know how hard it is to contain the urge to start coding as soon as we can. After the first sprint planning, our fingers – uncontrolled, hungry creatures – want to start smashing the keyboard, translating our ideas into code fastly and furiously.
Despite how great we feel while developing, it’s always a good idea to take a step back, especially when building something that could be used by many different users – like an API is. A. In this post, I’ll show you why and how to design a properly-thought API.
