Every year Apple promises something very special and something that has never been seen before at their keynotes. This year they already delivered — though not (yet) in any announcement fashion. Due to COVID-19, this is the first year their annual world-wide developer conference (WWDC) is held online-only.
While other major companies also had to make this switch due to the pandemic it is interesting to see how Apple is adapting to the situation as their WWDC is one of the longest-running annual conferences. Its first edition was in 1983 which is a stunning 37 years ago.
Apple already released a broad outline of this year’s edition. Starting with the keynote and the Platforms State of the Union they announced 100+ engineering sessions as well as 1-on-1 developer labs. Already a couple of days before the event they opened up their brand-new forums for developers. …
One of the greatest powers of Apple’s iOS platform is the diversity of built-in frameworks. There are many gems to be found which provide easy-to-use but advanced functionality. One of these examples is the
Vision framework which was introduced in iOS 11.
The goal we want to achieve in this tutorial is to implement an on-device text recognition app, which allows our code to work even without an internet connection. In addition, we want to be able to scan documents right from our camera feed and extract the text from there. …
In this ongoing series, I want to analyze the building blocks of SwiftUI, which is Apple’s new, cool, and hip declarative UI Framework.
One of the most common tasks when building a UI is to display text. This is why I want to start this series with the respective element for SwiftUI which is (un-)surprisingly called
We will go over different chapters on how to use
Text and some of the more and some of the less common things we can do with it.
The first thing that is important to note is that all UI elements in SwiftUI are
Views. This sounds rather abstract at first but if we take a closer look this only means that they have to conform to the
View protocol. …
In this ongoing series of blog posts called Machine Learning Basics I want to cover the underlying core concepts of modern machine learning. While it seems that more and more people are just throwing neural networks at problems it is utterly important to know how things work under the hood. This gives a more intuitive understanding of the process and maybe offers insight into different solutions and approaches.
Warning: These posts will be containing a lot of math. I’ll do my best to explain everything in an easy and comprehensible way and provide further links if necessary. If you can’t follow then don’t worry, these concepts are hard and need some time to sink in. …
When working with Python in different projects on a single system the problem of package and version management can get really frustrating. Some projects may require an older Python version like
2.7(you should definitely look to upgrade) compared to another one that needs
3.7. Maybe different packages depend on different versions of other packages and you break dependencies in places you don’t even know by updating packages.
In the beginning it may seem like an overhead to use a different environment for every project. …
As you might have read in my previous post I like Flutter. There’s a lot to read on why it could also be cool for you to try out but this post covers something different.
As a matter of fact I not only like Flutter but I also like Machine Learning. The thought of a machine that is learning how to perform a task has a huge fascination on me. So of course the natural process was to combine these two topics. And what better way to start off the process than Google’s very own MLKit.
It was introduced at Google I/O in 2018. The basic idea is to open up access to their Machine Learning magics and make them available to mobile developers. There is a lot of documentation for Android and iOS but I guess they’re still perfecting the Flutter versions to meet the high standards of the docs on the Flutter website. …
Flutter is the new, hip cross-plattform, open-source, mobile development framework made by Google. What does that mean? It means one codebase to rule them all. No need to dig into Swift/Objective-C to build an iOS app and rebuild the whole thing with Kotlin/Java.
So why create another framework? Well one theory is that Google just wants to jump on the bandwagon and hacked up something quick to build just another framework. That’s wrong. It was definitely not a quick shot but a well thought out creation. Why? …