As mentioned in my last post, I’m working on an Audiobook player for my employer.
As a part of the project, my team and I have published a plugin for NativeScript to make it easier to access accessibility features for both Android and iOS.
The target audience for our project are people with dyslexia or visual impairment, this makes accessibility is key feature for us.
Unfortunately this is one of the few things NativeScript doesn’t do very well. We’ve provided a few patches to fix accessibilityLabels, but beyond that finding a common abstraction for both platforms is probably not possible. The way Android and iOS do accessibility is just too different. It’s possible to do it in code, but we’d rather do it in template.
React-Native have a pretty nice API using the platform specific accessibility features.
For our needs and inspired by the React-Native API, we’ve released @nota/nativescript-accessibility-ext — sourcecode.
The plugin is a work-in-progress and in time we’ll go beyond what React-Native provides.
The plugin extends NativeScript’s View-classes with new properties and can be used both with and without nativescript-angular.
In-time a demo App will be available, but not at the moment.
On the 6th October I held my first ever public talk at AngularJS Copenhagen on the topic: “Cross-Platform Development – Using Angular 2 & Nativescript”.
I talked about an extremely cool project I’m working on for Nota, an Open Source audiobook player for iOS and Android. and the challenges in such a project.
It was a great success and I got a lot of possible feedback from the audience.
On 30th April 2014 I said goodbye to GoLease.com.
I’ve enjoyed working with GoLease.com, it has been a nice challenge and I’ve had some wonderful colleagues, who I’ll miss in the future.
Today 19th May 2014 I’ve started my new job as a web-developer with Nota.
I’ll be working on tools for people with reading impairment (Dyslexia and visual impairment). I’m looking forward to the new challenges and my new colleagues.
WebPerfM (horrible name I know) is a performance test tool for websites.
The idea came from the need for reliable performance test to know if a given site can handle a certain number of concurrent users.
For it to be a reliable performance test, it must act as close to real user behavior as possible.
The presents the problem of writing these tests, there have to be many different tests and they all have to be written like real user behavior.
Luckily we can create these tests without having to invent them.
Open Web Analytics (OWA) is a analytic tool like Google Analytics that you can host on your own server. OWA stores complete real life user sessions on the site in a accessible MySQL database.
So the idea is that WebPerfM reads the OWA database and crawls the website just the users did.
Each session is a list of what pages the user visited and what the delay between each pageview were.
WebPerfM runs multiple sessions at a time.
So far WebPerfM is just over the proof-of-concept stage and there a few things missing:
- Scaling of how many concurrent sessions
- Set number of sessions
- Set age of session from the tests are created
- Proper caching of js-, css- og image-files with handling of ETAG, expire-date etc.
There are some limitations:
I can’t simulate logged in users.
On the 12th August 2013, I’ve started working for GoLease.com as their new webdeveloper.
GoLease.com is Denmark’s largest trade portal for leasing equipment to companies and individuals.
I’m looking for to my time with this new company and hope it will be as great a time as I had working for Peercraft.