Announcements

Todays blog post is less technical than the previous ones. I would like to talk about some events that happened in the last time. I am a registered Apple developer since November 2013. Since then I collected a lot of experiences, built a lot of apps and gained a ton of knowledge. But every product I built was for someone else, no matter if it was a company or a person. »

Technical details

(The cover is copied from http://coub.com/view/7x8n3. If you do not know what the picture has in common with the topic, check out last weeks blog post) Last week I introduced ‘Get Schwifty’ - an app to write, evaluate and run Swift scripts on an iPhone. Today I am going to describe some technical details of the project. The project consists of three major parts: user interface, compiler and JavaScript runtime environment. »

Introducing Get Schwifty!

Each year Apple organizes a conference for their third party platform developers. The conference is called WWDC (world wide developers conference) and takes place in California, USA. Although the tickets are extremly expensive (1,599$ each) it is almost impossible to get the chance to buy one due to the mass of people who try their luck. The conference is all about the software; Apple uses the opening keynote to introduce the new major versions of their platform operating systems, iOS and macOS. »

React Native Example

In this post I am going to describe what steps are necessary to create an app in React Native. The example I want to build is the same one I created during my Cocoaheads talk. If you would like to see this in action or get more information check out my last post here. Installing dependencies You may already know this: in Javascript it is all about dependencies. The language itself is pretty easy and does not have a lot functionality. »

Benjamin Herzog on #react,

About React Native

In this blog post I would like to talk about React Native. Before starting: this evening I am going to talk about this topic at the Cococaheads Dresden meetup. If you are more the visual type and you are able to understand German check out the video of the talk here. React Native - Learn one, write anywhere: Build mobile apps with React. This is the official description of the framework and you will get what it means during this post. »

Benjamin Herzog on #react,

Fast feedback using a REPL

In this blog post I would like to write about the REPL which I built to get a fast feedback cycle for my lexer. Before going into the topic, here is a short description of what REPL stands for and what its purpose is. REPL stands for Read-Evaluate-Print-Loop. So in the end it is an endless loop which is waiting for input from the user to evaluate it and print the outcome afterwards. »

Writing a lexer

If you have read last weeks blog post you might also have checked out the repository of my compiler on Github. After deciding which programming language to use and decided on the name for the project I started creating the first fundamental files. One of them is the lexer. Before diving too deep into the topic here is a definition of lexical analysis from Wikipedia: In computer science, lexical analysis is the process of converting a sequence of characters […] into a sequence of tokens […]. »

Starting the challenge

As mentioned in the last blog post I am finally able to start my challenge for this year. In an earlier blog post I thought about some key points that need to be decided before I can finally start. Here is the list with their short answers, the long answer is written below: In which main language will the tools be written? Go Will the language be compiled or interpreted? »

I am done

Today I wrote my last exam for this semester; so I am finally done with this stressful time. It feels like it is getting harder every time to concentrate only on the topics that are necessary to pass every single exam. Especially in this time my head is full of motivation for a lot of different projects but I am forcing myself to not start any of them during the exam period. »

Part 3/3 - It's all about the mapping

All Parts: 1 - 2 - 3 Last week I defined the interface of the Client and its Authenticator. Together with the definition of the endpoints (first part) it is now possible to take a deeper look into the actual network request. But before doing that I need to clarify one important part: the mapping of the response. Mapping JSON (or other transport formats) is a different topic, especially in Swift. »