CSS-essentials, Onefootball open source CSS project
Working daily on our [onefootball webapp] (https://www.onefootball.com), we come across a lot of different design challenges. As we all know, with complexity of design, complexity of CSS rises.
Onefootball Tech Blog, from Berlin with love
Working daily on our [onefootball webapp] (https://www.onefootball.com), we come across a lot of different design challenges. As we all know, with complexity of design, complexity of CSS rises.
Onefootball app is designed with the goal to deliver the best suitable football content for each individual user. In order to achieve this our backend hourly handles great volumes of data. It’s a good practice to keep track of processed data, especially when it comes to football results, where sequence of parsed files is equally important to the content.
[(CSS) Sprite] (https://en.wikipedia.org/w/index.php?title=Sprite_(computer_graphics)&redirect=no#Sprites_by_CSS) is a method, where we combine multiple small images or graphic into one large image and access the needed graphic by specifying ‘coordinates’ on the big image. The main reason behind it is to improve performance of website. To understand this better, we need to be aware of browsers technical limitations.
We recently struggled with a very annoying issue in our android app: It was extremely hard to debug because we were not able to reproduce it properly. Still we got quite a few reports about the bug from users, so we decided do ask them for help debugging the app. In this article I will describe our experiences. Even if you develop for other platforms than android, our experiences might be usefull for you. So keep reading!
Apple introduced in Xcode 7 UI testing that allows developers to easily test their user interface, but if you try it yourself you will soon discover that tests are not executed in isolation. The application starts where it was left off and it can be very problematic if your application has a state that you modify through your tests. Eg. some kind of on-boarding, creating records and so on.
We’ve recently heard a lot about ChatOps and are thrilled by the possibilities and chances. So we introduced Onefootbot as our company robot based on Hubot connected via HipChat. github wrote Hubot to automate their company chat room. Later they released it as open source. It is written in CoffeeScript on Node.js and can easily be extended or customized by your own scripts. The general idea behind it is to bring your tools into your conversations and use the chat bot to work with plugins and scripts so teams can automate tasks and collaborate, working better, cheaper and faster.
You don’t necessarily want to enable analytics tracking when testing your application on your local machine, nor do you want to log all of the debug messages on your production server. Here is a simple solution to handle multiple application configurations depending on the environment it’s running in.
A few months ago we suddenly faced a very strange problem. Our webapp looked completely broken in a very specific version on iOS inside a web view of another iOS app. Something was wrong with our Javascript code, but only on this particular context. First thing that came to our minds: “how are we going to debug this if we don’t even have access to our usual development tools?”
Gozure is a Go(lang) backend client for Microsoft Azure Notification Hub. It is a simple REST API wrapper that we internally use in our Go projects.
On the surface, Onefootball is an awesome app for football fans to get their daily dose of news and scores wherever they are. But if you dig a bit deeper, you’ll find that Onefootball is also a team of professionals solving challenges in many domains. One of those domains is software engineering and that’s what this blog is about.