Views, Graphics, and Drawing

The Android platform is designed to operate on a variety of different device types, screen sizes, and screen resolutions. To assist developers in meeting this challenge, Android provides a rich toolkit of user interface components to utilize and customize to the needs of their specific application. Android also relies very heavily on an extensible XML framework and set resource qualifiers to create liquid layouts that can adapt to these environmental changes. In this chapter, we take a look at some practical ways to shape this framework to fit your specific development needs.KeywordsJava CodeOutput AreaUser PressPublic ClassCustom WidgetThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

For the first year or so after Android 1.0 was released, all production Android devices had the same screen resolution (HVGA, 320×480 pixels) and size (around 3.5 inches, or 9 centimeters). Starting in late 2009, though, devices started arriving with widely disparate screen sizes and resolutions, from tiny QVGA (240×320) screens to much larger WVGA (480×800) screens. In late 2010, tablets and Google TV devices appeared, offering yet more screen sizes, and with the release of Honeycomb and Ice Cream Sandwich, tablet and larger screen sizes exploded.

In user interface design a common pitfall is to use the technical properties of the device as basis for the design, which easily causes a user interface to become too complicated and hard to use. Also, the great development in the area of different hand-held terminal devices has set new requirements for user interfaces: screen sizes of devices are very small, advanced I/O devices are used instead of ordinary mouse and keyboard and the operating environment of the devices differs significantly from familiar PCs and laptops. However, governmental and in particular military communications systems often trail behind this development. To be able to overcome the aforementioned challenges and take usability of governmental communication systems to a new level, a new approach is needed. This paper covers user-centered design of graphical user interfaces to advanced communication devices designed to be used in challenging environment, e.g., in moving vehicles and outdoors in any season, and to support devices with limited screen size and touch screen technology. We also introduce a proof-of-concept implementation and show through a user test that general principles introduced in the paper can easily be applied to a specialized communication device.

This paper introduces the overall structure of the hierarchical structure and car Android platform of interactive systems, analyzes the system design and implementation process of each function module.The trial was carried out in the HTCS710e mobile phone and Motorola Xoom tabletcomputer, the test results show that the system has stable operation, friendly man-machine interface, can basicallyachieved our goals at the beginning of design.

ABSTRACTPrevious studies on mobile Web browsers have focused on phone features and technical performance, but not on the user interface. In this study, we compared three mobile Web browsers in the iPhone and ultimately proposed recommendations for the design of mobile Web browsers for smartphones. To develop such recommendations, we redefined the user interface (UI) components of mobile Web browsers from previous studies to conform to smartphones and compared the Chrome, Safari, and Opera Mini-browsers. To do this, we conducted experiments on usability tests with several dependent variables, including usefulness, perceived time reduction, minimal action, usability, ease to memorize, learnability, fun, and satisfaction. Finally, we developed several recommendations, based on the experimental results and participant interviews, which will fulfill user needs for the interface design of mobile Web browsers for smartphones. Multi-windows need to be implemented in a 3D environment. Developers should consider UI components and features that ease learning how to use the browser for novice users.

In the last years, the types of devices used to access information systems have notably increased using different operating systems, screen sizes, interaction mechanisms, and software features. This device fragmentation is an important issue to tackle when developing native mobile service front-end applications. To address this issue, we propose the generation of native user interfaces (UIs) by means of model transformations, following the modelbased user interface (MBUI) paradigm. The resulting MBUI framework, called LIZARD, generates applications for multiple target platforms. LIZARD allows the definition of applications at a high level of abstraction, and applies model transformations to generate the target native UI considering the specific features of target platforms. The generated applications follow the UI design guidelines and the architectural and design patterns specified by the corresponding operating system manufacturer. The objective is not to generate generic applications following the lowest-common-denominator approach, but to follow the particular guidelines specified for each target device. We present an example application modeled in LIZARD, generating different UIs for Windows Phone and two types of Android devices (smartphones and tablets).

Creating a digital Manga comic for mobile devices is chalenging because of the limitation of device's screen size and time consuming of the process. In this paper, we proposed an efficient method for automatically creating mobile content of digital Manga comic from scanned of printed digital comic by extracting comic frame, comic balloon and Japanese character within a Manga comic then recompose it a new mobile content using ComicXML to store comic frame content information. Experimental results on Manga content extraction have 81.6% accuracy of non-flat comic page frame extraction, 100% accuracy of comic balloon detection, and about 93.75% accuracy of Japanese character text extraction.

Nowadays, touchable displays are widely used in most embedded systems, including mobile phones and other hand-held devices. Although interactive user interfaces are intuitively required for these systems, most of interactive graphical user interface implementations usually need lots of system resources. For low-tier embedded systems, we have presented that the text-based user interfaces are more suitable, as shown in our previous works. In this paper, we present an object-oriented approach to provide a full-scale text-based user interface scheme, especially on the low-tier embedded systems. Our application user interface implementation is very simple and intuitive, with few amount of computing resource. It naturally supports multiple overlapping windows, pop-up menus, pull-down menus, dialog boxes, and other user interface components, with graceful object-oriented application programming interfaces. We also provide large size text output for emphasis purposes. All the systems are now available as a software library, and can be used for wide range of applications.

User interfaces for iOS devices must adapt to different screen sizes. Not only are there different-size screens for the iPhone and iPad, but there are also different screen sizes among different iPhone and iPad models on the market. To solve this problem, SwiftUI centers user interface items, but what if you need to precisely place user interface items in specific locations?

Migrating to Android for iOS Developers gives youas an experienced native iOS app developerthe skills to learn native Android apps development from scratch. Starting with preparing your Android integrated development environment and introducing just enough Android application framework fundamentals, youll understand how to create a simple but meaningful HelloAndroid project immediately. This book provides the guidelines and tutorial projects to show you how to translate your existing iOS app to the Android platform. Youll use your mobile app knowledge to structure your Android apps in a similar way to how you would structure your iOS apps. To implement use cases with detailed screens, the most common mobile topics are discussed, including user interfaces, managing data, and networking with remote services. As you move through the book, youll create Android apps with rich UI components to handle common CRUD operations locally and remotely. There are many Android goodies described in the book. Instead of relying on routine text descriptions, youll discover the uniqueness of Android and appreciate the many features that are unique to the platform. This book also explores more powerful mobile UX patterns that are commonly used on the iOS and Android platforms. When you finish reading Migrating to Android for iOS Developers, youll be an Android developer as well as an iOS developer. And, you will be fully convinced you can do everything in Android that you can do in iOS. What youll learn How to maximize your existing iOS mobile knowledge to learn Android programming skills How to use the Android integrated development environment with the Eclipse ADT plugin How to translate your existing iOS code to Android with the following common mobile topics: Common mobile screen navigation patterns User interface components and UI animations Storing data Networking and using remote services Using system apps Maps and location awareness Mobile search frameworks Mobile analyticsWho this book is for This book is for iOS app developerslike youwho want to port their native iOS app to become an Android app. Also, if you are not an iOS developer, but already familiar with mobile apps, then this book can also help you understand Android development with step-by-step instructions and tutorial projects.

Many executives take for granted that the first company in a new product category gets an unbeatable head start and reaps long-lasting benefits. But that doesn't always happen. The authors of this article discovered that much depends on the pace at which the category's technology is changing and the speed at which the market is evolving. By analyzing these two factors, companies can improve their odds of succeeding as first movers with the resources they possess. Gradual evolution in both the technology and the market provides a first mover with the best conditions for creating a dominant position that is long lasting (Hoover in the vacuum cleaner industry is a good example). In such calm waters, a company can defend its advantages even without exceptional skills or extensive financial resources. When the market is changing rapidly and the product isn't, a first entrant with extensive resources can obtain a long-lasting advantage (as Sony did with its Walkman personal stereo); a company with only limited resources probably must settle for a short-term benefit. When the market is static but the product is changing constantly, first-mover advantages of either kind -- durable or short-lived -- are unlikely. Only companies with very deep pockets can survive (think of Sony and the digital cameras it pioneered). Rapid churn in both the technology and the market creates the worst conditions. But if companies have an acute sense of when to exit -- as Netscape demonstrated when it agreed to be acquired by AOL -- a worthwhile short-term gain is possible. Before venturing into a newly forming market, you need to analyze the environment, assess your resources, then determine which type of first-mover advantage is most achievable. Once you've gone into the water, you have no choice but to swim.

ABSTRACTComputer‐based tests administered in established commercial testing centers typically have used monitors of uniform size running at a set resolution. Web‐based delivery of tests promises to greatly expand access, but at the price of less standardization in equipment. The current study evaluated the effects of variations in screen size, screen resolution, and presentation delay on verbal and mathematics scores in a sample of 357 college‐bound high school juniors. The students were randomly assigned to one of six experimental conditions—three screen display conditions crossed with two presentation rate conditions. The three display conditions were: a 17‐inch monitor set to a resolution of 1024 × 768, a 17‐inch monitor set to a resolution of 640 × 480, and a 15‐inch monitor set to a resolution of 640 × 480. Items were presented either with no delay or with a five‐second delay between questions (to emulate a slow Internet connection).No significant effects on math scores were found. Verbal scores were higher, by about a quarter of a standard deviation (28 points on the SAT® scale), with the high‐resolution display.

There is a significant increase in mobile internet usage resulting in demand for traffic volume, frequency efficiency and energy and cost reduction, for which small cell networks are expected to play a key role. Due to high bandwidth requirement, mobile health applications (m-health) and medical video streaming in particular will benefit from small cell networks in terms of Quality of Service (QoS) and Quality of Experience (QoE) enhancements. This paper presents content-aware and device-aware medical Quality of Experience evaluations in terms of subjective (e.g. MOS) and objective (e.g. PSNR and SSIM) quality metrics obtained over small cell networks. Furthermore, we address the following two main research questions: (1) How significant is ultrasound video content type in determining medical QoE? (2) How much of a role does the display device play in medical experts’ diagnostic experience? The former is answered through the content classification of ultrasound video sequences based on their spatio-temporal features and validating their significance through medical experts’ subjective ratings. The latter is answered by conducting a subjective experiment of the ultrasound video sequences across multiple devices, ranging in screen size and resolution.

A new television system based on the Autosophy information theory is now being developed for Internet video applications. Autosophy communication is already widely used on the Internet, with current applications including data compression in V.42bis modems, and the lossless still image compression standards GIF and TIF. Now Autosophy Internet video is being developed and is ready for demonstration. In conventional television, bit rates are determined entirely by screen size, resolution, and scanning rates. The images shown on the screen are irrelevant, such that random noise video requires the same bit rate as any other video content. In the new Autosophy-based television, in contrast, bit rates are determined entirely by the video content, essentially motion and complexity within the images. A very high degree of visually lossless video compression is possible because only moving portions of the video are transmitted. Transmitted codes represent multi-pixel image clusters found in a pre-grown hyperspace library. The system can dynamically reduce resolution of fast-moving objects when necessary to accommodate bandwidth restrictions. Ideally suited to the Internet environment, the new television also features high resistance to delayed or dropped packets, a universal hardware-independent communication format, and optional codebook encryption for secure communications.

Development of GUIs (graphical user interfaces) for multiple devices is still a time-consuming and error-prone task. Each class of physical devices - and in addition each application-tailored set of physical devices - has different properties and thus needs a specifically tailored GUI. Current model-driven GUI generation approaches take only few properties into account, like screen resolution. Additional device properties, especially pointing granularity, allow generating GUIs suited for certain classes of devices like touch screens. This paper is based on a model-driven UI development approach for multiple devices based on a discourse model that provides an interaction design. Our approach generates UIs using an extended device specification and applying model transformation rules taking them into account. In particular, we show how to semi-automatically generate finger-based touch screen UIs and compare them with usual UIs for use with a mouse that have also been generated semi-automatically.