This incorporates conceptual work, programming and a huge portion of consulting. He always strives for clean and easy solutions. Cathy is a User Experience Manager at RNIB and together with her team works with companies on their products, websites and apps to improve the usability and accessibility for blind and partially sighted people.
This includes design, heuristic assessments and user testing with blind and partially sighted people. As an app marketing consultant, Laura is making sure that app companies are set for success now and in the future. One of her major fields of expertise is advising apps on their app store optimization activities.
If you want to know how to drive conversions and gain visibility in the Google Play and Apple App Store, she is the one you should turn to. Together with the graphic design department at Customlytics, she is developing engaging creative assets for app product pages in the stores - and she has eagle eyes for any askew alignement. Other areas of her expertise include mobile CRM topics and tracking. He lives in the Seattle area and enjoys downhill skiing and fly fishing.
Julian's mission is to help people live better lives through mobile technologies. He has worked globally in leadership and engineering roles for Google, eBay, Salesforce, Klarna, Badoo, and many others to help improve engineering practices and deliver better quality software while also improving the fulfillment and motivation for the people involved.
He has been actively involved in the modern mobile ecosystem since and this guide from onwards. He is also trying to complete his PhD on improving development and testing of mobile apps. Twitter: julianharty. GitHub: github. Dennis is the Managing Director and Co-Founder of swenden. He consults clients in the field of digital product development. Topics cover conception, implementation and product validation. Everything in a lean way.
From time to time you will find him giving workshops and speaking about his experiences and knowledge.
Marc is a mobile app test expert at Polteq and has worked in different test roles for over 14 years. He is helping companies with test process improvement TI4 Mobile approach , mobile device analysis, mobile test strategy, implementing mobile test automation and giving the in-house developed mobile trainings mobile app testing foundation, mobile automation, API manual and automated testing.
Currently Marc performs research for Polteq on testing AI, is program chair for the Polteq conference and is running projects for multiple companies. Robert has worked in the mobile industry for more than 20 years.
In his spare time, he likes to draw, play with his retro computers and spend quality time with his family. He is currently product manager for e-mail and chat apps at Open-Xchange. Mastodon: mastodon.
Sarah is an apprentice for digital media design at Open-Xchange. She is also responsible for the design of this guide. In her time off she likes to play video games and to create digital illustrations.
Cornelius specializes in graphic, UI, UX and visual design for mobile applications and other interactive technologies. He was in charge of the layout and design of the previous guides. When not involved with something mobile, he loves to experiment with digital art and illustration. That means she is engaged with User Interface, User Experience and graphic design for mobile applications, as well as coding. Porting Frameworks Porting frameworks automatically adapt your application to different devices and platforms.
Such frameworks typically feature following in- gredients: — Client library that simplifies development — Build tools chain that converts code and resources to application bundles — Device database that provides information about devices — Cross compilers to port your application to different platforms In the J2ME world there are various frameworks to choose from: Xpress Suite from JavaGround1 provides porting against revenue sharing.
Cel- sius from Mobile Distillery2 is licensed per month. Bedrock from Me- tismo3 provides a suite of cross compilers on a yearly license fee. Good porting frameworks allow you to use plat- form and device specific code in your project, so that you can provide the best user experience. In other words: A good framework does not hide device fragmentation, but makes the fragmentation manageable.
A Question of Trust: Certification The mobile Java standard differentiates between signed and unsigned applications. Some handset functionalities are only available to trusted applications. Which features are affected and what happens if the ap- plication is not signed but uses one of those features largely depends on the implementation.
Most implementations also differentiate between the certification authorities who have signed an application: Applications signed by the manufacturer of a device enjoy the highest security level and can access every handset they desire.
Applications signed with a carrier certificate are on a similar level. Applications signed by JavaVerified1 , Verisign2 or Thawte3 are on the lowest security level. The mad thing is that not every phone carries all necessary root certificates.
And some well known vendors even strip away all root certificates. The result is quite a mess, so consider sign- ing your application only when required, e.
Thanks to the universal app stores, nowadays distribution is easier than ever. They manage the payment, hosting and advertisements and receive a revenue share for that.
Sprint5 or O2. When discussing the mobile internet, the first question is: Why shall I setup a special website for mobile devices? On one hand there are automatic adaptation engines like Google or Opera Mini , which automatically generate mobile versions of any web- site. On the other hand, the mobile browsers are getting more powerful and capable of displaying any website e. The mobile usage is totally different. When using internet on the mobile handset, the user is usually on the move. He wants to know more about his surrounding or just fill some minutes.
Applications have to take these differences into account. For example, a search mask for stationary users has to offer comprehensive options, on the mobile handset it has to be more straight-forward, focused on the certain action. These adjustment cannot be realized by a machine. This is one reason why it is indispensable to create special mobile versions of web- sites. This means, the content of a mobile website has to be arranged accordingly: Images should not be too large, all relevant elements should be easily accesible although the user is not able to move a cursor freely along the site.
The best is to test the usability of a site under real-life circumstances: Take your mobile handset to a busy public place and try to find all relevant info of your application by just using one hand. You will see very quickly where your mobile site shall still be trimmed. But apart from things like markup, image formats and navigation, you should never forget about the most valuable good of the mobile user: Battery power. Complex websites with a lot of JavaScript, CSS and Flash elements need a lot of processing power which means battery power.
Some History on the Mobile Web WAP: The stone age of mobile internet In the beginning, everybody in the business expected the mobile internet to be a cashcow. Many players expected to get rich by selling information which was already available for free on the internet. The usage of images was limited to black and white pictures which were a lot less sexy than what the users knew from their home computers.
How to adapt content for the mobile user Static Version Of course you can simply ignore the possibilities of automatic optimi- zation and leave it up to the user: Create different versions of your content, let the user start with the most low-level version and let him decide manually which variation is the most comfortable one for his device and usage patterns in a next step.
But since you are dealing with a user who is on the move and does not want to spend a lot of time with finding out how to see properly what you are delivering, this is probably not the best way to go… Automatic adaptation technologies To adapt the content to different devices, you basically need two com- ponents: One logic that detects the device, knows about its browser and its characteristics — a device database. The second component interpretes these characteristics and adjusts the content accordingly.
A lot of tools deliver APIs for detecting the browser, delivering its properties and adjusting the content, the markup and the images. But of course there are also purely commercial providers. Again, some are concentrating on device data and detection, others are focusing on offering software platforms which adjust the content accordingly. Examples for commercial device data and device detection providers: — dotMobi1 offers several APIs to access their device database DeviceAtlas2 and intelligent detection — DetectRight3 Some commercial content adaptation software providers: — Sevenval4 , a platform independent technology which works via HTTP and markup.
This solution is available as a Service or can be installed on Linux systems. There are two versions available: one Open Source Community version and one professional version. Satisfy the Interpreter of Your Content: The Browser Markup Of course it would be great if there would be one universal markup standard — unfortunately this is not the case.
There are many stan- dards, so be sure of validating your markup. Furthermore it is always good to stick to UTF-8 encoding. Page Width Always use dynamic layout. Avoid static width settings in pixels, better use percentage values. Even when using device databases, the brows- ers still have different display methods fullscreen, landscape, por- trait and only some allow displaying a scrollbar. The web is dynamic, so is the hardware landscape — keep your layout dynamic as well! Images Not everybody has a mobile data flatrate, so do not use images too excessively, avoid any unnecessary images.
To reduce data and proces- sor workload, the images should always be scaled on the server and not by the browser. Of course PNG offers more flexibility, but when it comes to transparency, you cannot always be sure to what degree it is sup- ported. And some operators still use image proxies which might not be able to handle this. Tables For stationary web, tables are no longer used for webdesign. CSS is simply not capable to assure this with all browsers.
CSS interpretation is sometimes not properly implemented and shortens battery life. When determining sizes, avoid to define them in pixels, use percent- age values. Fonts Do not deal too arbitrarily with fonts: all browsers just dispose of a limited set of font-types. Better focus on the font size. Cookies You can of course use cookies and should do so, but only when really needed. And never trust too much in them: although it might work fine during one session, the cookie might get lost afterwards.
This is why you should always offer alternatives like an URL based param- eter or a personalised bookmark for permanent settings. So it would be wrong not to use the possibilities of these technologies. But you should make sure that your side works fine without them as well. Then you should start low-level and implement a tool which detects the devices who are accessing your site.
Several providers are offering this kind of analysis software: — Sevenval www. Surfing the internet with much older devices is no fun anyway.
Touch Devices Here it is referred to modern devices with a powerful browser like the iPhone or Android handsets. The touch-sensitive UI offers the possibility to move more freely within a website. Labels enhancement imap. Copy link. In particular, server implementations MUST preserve the exact form of the modified BASE64 portion of a modified UTF-7 name and treat that text as case-sensitive, even if names are otherwise case-insensitive or case-folded.
Listening to new emails seems to be not working in high-level api Member Author. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment.
0コメント