Midterm support and development of Mobile Applications

screen-shot-2016-12-15-at-16-42-33

Code legacy, project member fluctuation, frequent code changes. Terms which make longterm projects and quality assurance challenging, this also applies to software. Now, with an iPhone app in store where the first line of code was written in Nov. 2013, … Weiterlesen

Software Testing (4/4) – Automated UI Tests

Diagram: amount of runs per use case

Former posts of this series always explained the solutions of the testing approaches. Let me now try to inspire you to understand my motivation in writing this series, as automated UI tests were my main motivator to finally increase the … Weiterlesen

Software Testing (3/4) – Integration Tests

TL;DR
A data model and the related database of course change from time to time. New features are introduced, old and deprecated data types are removed and new relations embedded. Data integrity ensures your application works as it’s supposed to. Consider two different scenarios:

  1. Another system introduces changes, which affects the API in whatever way. You are able to say for sure, no changes of your own system lead to this error and you can easily take action to solve this issue instead of tracking down the instance which could have been responsible for the error. In theory ;-)
  2. Some changes lead to side effects and affect other test scenarios. React on them and keep everybody’s daily-business up and running instead of facing a problem several days after a change, when the error finally occurs.

At last: be honest. How many times did you think: „This solution is engraved in stone, my children’s children will still benefit from this“ – and now let’s face reality ;-)
(mehr …)

Software Testing (2/4) – Unit Tests

TL;DR
Unit tests are a a great way to ensure that a function behaves as intended and returns the expected result. The idea is to only test a specific function or method and thus ensure the reliability of a small brick in the wall, which shall not be tested all over again and again by the user. (mehr …)

Software Testing (1/4) – Introduction

Testing pyramid - illustrating the kinds of existing software test opportunities

First of all, I do not want to discuss what kind of software developing process one should choose or prefer. If it’s either TDD in combination with Scrum or Waterfall – I don’t mind. The intention of this series about … Weiterlesen

Xamarin – Cross Platform Mobile Development (3/3)

visualstudio_xamarinstudio

After examination of the present native mobile app development challenges in part one and the introduction in Xamarin in part two of this blog series, the final part comprises insights and learnings out of direct project practice. In the last … Weiterlesen

Xamarin – Cross Platform Mobile Development (2/3)

Xamarin

The concept of Xamarin as a Mobile Cross Platform Development toolkit can be best summarized with following statement: “Create native iOS, Android, Mac and Windows apps in C#” This is a post of the blog series “Xamarin – Cross Platform … Weiterlesen

Xamarin – Cross Platform Mobile Development (1/3)

Mobile Devices

Mobile here – mobile there, by now everything has to be mobile accessible at least. Thereby one has to distinguish between mobile optimized websites, pure web-apps and classical native apps. The latter has to be dedicated developed for a specified … Weiterlesen

Präzise Position nun auch in Gebäuden bestimmbar? Wir haben die iBeacons des neuen iOS7 getestet

Raumplan

Navigation mit GPS auf dem Smartphone ist jedem bekannt (Google Maps etc.). Sofern die Satelliten Signale oder die Signale zusätzlicher GPS-Empfänger das Gerät erreichen können, ist eine Positionsbestimmung sogar zentimetergenau möglich. In Gebäuden ist das leider selten der Fall. Wer … Weiterlesen

Mobile Crossplattform Entwicklung auf Basis von Phonegap – Ein Erfahrungsbericht

Ameisen sind fleissig, tatkräftig, rastlos und oft unterwegs, haben aber kein Internet.

Ähnlich geht es den Namics-Mitarbeitern auf so manchem Außendiensteinsatz, die trotzdem auf verschiedene Services angewiesen sind, wie der Zugriff auf sämtliche Mitarbeiter Kontaktdaten, der nicht immer online erfolgen kann. Die in die Jahre gekommene, mobile Weblösung sollte mit einem mobilen Telefonbuch abgelöst werden. Da bei Namics jeder sein eigenes Mobile Phone nutzen darf (BYOD-Philosophie) muss die erstellte Lösung auf möglichst vielen Plattformen laufen. Die Devices sind zu ca. 80% auf iOS und Android verteilt und diese Devices sollen primär auch unterstützt werden.
(mehr …)