Development and maintenance of information systems is a big expense. In Ackee, we focus on the whole process of application creation from its specification through the design and development to the testing. That is why we know that the road from the idea to a finished app in the store can be complicated, long and expensive. So how to make sure that your application does not cost too much? (more…)
Over the last few years Android Developers have established best practises for writing apps: clean architecture, usage of MVVM as primary architectural pattern.
The most discussed topic of 2019 was modularisation. While it brought us a lot of benefits, I’ve discovered some pitfalls, one of them being in-app navigation.
Apple has recently announced a new ArgumentParser library that leverages property wrappers and is a great example of a well-written declarative API. But the declarative nature of it comes with some drawbacks – mainly that if you need to do something custom that the library is not built for, you will need to get creative. (more…)
Using domain exceptions in your app is an important step if you want to create abstractions over different 3rd party networking libraries like Retrofit or gRPC. Handling and mapping of these exceptions can quickly become a boilerplate that you and your colleagues have to think about and sooner or later you will probably forget to do it somewhere in your code. I want to explore how this task can be done automatically in a generic and clean way when using the Retrofit library. (more…)
Clean Architecture is a much-discussed topic in recent years not only in the Android community. You can find many articles about it and most of them are devoted to an explanation and implementation of the Dependency Rule, which is the basis of the Clean Architecture. Implementing the Dependency Rule is quite easy but it is also really easy to violate it and it can be really hard to uncover that on the code review. It would be possible to control it better using `package private` visibility or divide app layers properly to separate modules. The problem is that we do not have `package private` visibility in Kotlin and layer modularization does not have to be a good or preferred architecture for our app. But don’t worry! We can use help from the static code analysis tool called detekt and I am going to show you how in this article. I expect that you already know and understand Clean Architecture including the Dependency Rule. If you don’t, I recommend this great article from Mario Sanoguera de Lorenzo. (more…)
The Xcode project file has quite a complicated structure and it brings unnecessary complexity where something simpler could be used instead. Thus we were very intrigued to move to project generation. Project generation has a lot of benefits – not committing Xcode files means fewer merge conflicts (truth be told, merge conflicts have become quite rare now!) and also clearer project settings. Unless you are a wizard 🧙♂️, you probably cannot read a project file fluently (and even if you can, it is still very hard to get familiarized with it).
Tezos smart contracts have matured a lot – and it’s time to use them in iOS apps, closer to the users’ hands. 😉 Throughout this tutorial we will write a smart contract using SmartPy.io and then move to Xcode and get a hands-on experience with interacting with our contract in Swift using generated code from tezosgen. Note that this tutorial will touch on the most important parts of RateMyTeam app and is not a complete step-by-step tutorial. (more…)
Do you want to develop a new application, but the complexity of native application development is detering you from doing so? Maybe the new concept of software development might help you. It is called progressive web application (PWA). Is it just another buzzword or can PWAs really replace native applications?