#device specification

[sharonjordan]

Android resolution testing

After uploading my work to the Android device, I decided to do some testing to find out what resolution worked best on this device, and ultimately understand what changes would need to be made to make the interface work for this device.

These photos show the test file uploaded onto the android device. The test file includes three pages with three images at different resolutions.

low res - saved at 72 pixels

med res - saved at 150 pixels

high res - saved at 300 pixels

My initial test file was produced with a resolution of 800 x 480 - but this loaded with a white border. So I Created a new file that was sized according to the resolution of the Samsung Galaxy Tab I was using - 1280 x 800. The results surprised me because I expected the file then to be a perfect fit. However, because of the menu bar across the bottom in ICS OS, the resolution is scaled to the remaining height. Therefore to fill the entire screen it is necessary for the background to fill an area of 1400 x 800 otherwise there will be thin white strips on either side.

This means that there will be some reworking of my interface to make the design work on this device, but on the positive side, the height is less of a problem, and it may be more about ensuring the background bleeds to the side of the stage far enough to cover the excess screen area.

With regards to the image resolutions, I was fairly impressed with all three and there was no significant banding of the background colours such as that seen on my playroom app. On the other hand the improvement in picture quality with the higher resolutions was noticeable, and I would argue that the image resolutions should be increased to a minimum of medium (150pixels) to ensure adequate user experience.

[sharonjordan]

Before I begin the process of reworking the technical architecture, I am considering whether to build specifically for Android so that I could demonstrate my apps working on a device. This page - and other pages linking from it provide useful information about screen res and android build environment.

[sharonjordan]

Iphone 4S resolution

I have decided to build the app for the iphone resolution - 640 x 960 on the basis that this would also work on an ipad. However, in the longer term it would be more appropriate to build a version specifically for the ipad to maximise the benefits of increased resolution and screen real estate.

I have also decided to create the background images for the ebook app in illustrator. This enables me to create vector based graphics that should reproduce better on the iphone 4S retina display.

[sharonjordan]

Screen orientation

As I am progressing through the wireframes, it has occurred to me that a vertical layout may not always be appropriate, and has raised the question about whether to enable the screen to shift orientation as the device is moved, or to fix it either as a horizontal or vertical app - but not both.

In considering these options, I have tried to think about how the children used the devices and apps in the session, and look at other apps on the marketplace.

It is particularly interesting to note that on iphone, the angry birds app is fixed to horizontal orientation throughout, whereas the water? app is fixed to a vertical layout. These decisions reflect the best orientation for the main functionality, and the rest of the app has been positioned in the same way to avoid any need for the user to continually turn the phone.

From my perspective, it will be hard to determine which orientation will suit every app that becomes part of this system, therefore I feel it is more appropriate to constrain it within each individual app in the system to produce the most usable interface. This will avoid too much turning, but at the same time enable flexibility to suit the content.

This decision also means I need to rework my wireframes so far...!

[sharonjordan]

Focal point...who is the primary audience?

Throughout my research I have been considering both the use of this solution as part of learning in schools and at home. I still believe this is the way forward, however it throws up an issue relating to my initial thoughts on a commercial pricing structure. As my work is at the forefront of this field, there are no precedents already set, so I have to look at similar systems and pricing models to understand the best way forward.

Initial pricing model

Schools purchase a subscription per class enabling access to all apps available in the system.

Parents purchase the apps individually or by subscription to the whole service.

Issues

The main issue with this model is that if a child's school has already bought a subscription and wants parents to use this resource for home learning, they will most likely provide the login details of individual children to the parents. Essentially children will access the resource for free at home, so there will be no further cost benefit to the business. This is beneficial to those children from families who for whatever reason may not be able to purchase the apps, by providing the same opportunities to all in the class. However for commercial longevity, ensuring that the solution is  continually developed and maintained, there needs to be a sustainable business plan in place.

I feel it is important that parents can also buy some or all of the apps in this service for instances where use is not driven by schools adopting the system. This highlights the need to work out a solution for all three situations:

School subscription, free child access at home

No school subscription, parents buy individual apps on app store etc. links to encourage parents to sign up to portal and get more apps

No school subcription, parents sign up to portal and can either access all the apps available or access the apps they have paid for.

Subscription model & app store launch

Given the desire to promote this resource to schools and subsequently for parents to use to aid learning practice, I think it would be more beneficial to offer a package for all apps and functionality with a range of subscription options - free 28 day trial, pay for 3 months, 6 months  or a year subscription

For commercial launch, this model would have to be researched in more depth to establish the potential uptake by schools, and the suggested subscription costs for schools and parents.

The app functionality could also be lauched separately as individual apps on the app store, providing further cross links to the portal and income. This would also catch the younger audience (3-4 year olds) who may not be attending a school.

[sharonjordan]

More pre-schoolers know how to use a smartphone than tie their shoelaces. Is this the future of child learning, or a potent image of 21st-century alienation?

www.guardian.co.uk/technology/2011/nov/18/techno-toddlers-a-for-apple?INTCMP=ILCNETTXT3487

An interesting article discussing the abilities of pre-schoolers (2-5 year olds) to use touch devices, mainly smartphones, and the connections to future methods of learning. This relates directly to my work, highlighting the currency of my work, particularly as it concerns younger children than educational apps are typically targetted at. My work is aimed at children aged 3-7, targeting the early years when children are learning through play.

[sharonjordan]

iPads and iPods 'are helping our pupils learn without realising they are doing it'

www.guardian.co.uk/education/2011/oct/30/education-ipad?intcmp=239

This article discusses the impact of the introduction of iPods and iPads into primary schools, demonstrating that Hertfordshire is not an isolated case. It suggests that this is a new and popular trend, which therefore places my work at the forefront of the field.