Group items tagged

Around the globe, various initiatives use the mobile phone to provide financial services to those without access to traditional banks. Yet relatively little scholarly research explores the use of these m-banking/m-payments systems. This paper calls attention to this gap in the research literature, emphasizing the need for research focusing on the context(s) of m-banking/mpayments use. Presenting illustrative data from exploratory work with small enterprises in urban India, it argues that contextual research is a critical input to effective "adoption" or "impact" research. Further, it suggests that the challenges of linking studies of use to those of adoption and impact reflect established dynamics within the Information and Communication Technologies and Development (ICTD) research community. The paper identifies three crosscutting themes from the broader literature-amplification vs. change, simultaneous causality, and a multidimensional definition of trust-each of which can offer increased theoretical clarity to future research on m-banking/m-payments systems.

Among the many websites that are out there, few are standards-compliant. Among those few, only a handful sport style sheets adjusted to the needs of handheld devices. Of those which do offer styling for handhelds, not all will fit the smallest, lowest-resolution screens without presenting the user with the ultimate handheld horror: namely, horizontal scrolling. The Opera browser runs on handheld devices of all screen sizes and resolutions, some of them only 120 pixels wide. We work for the company that produces Opera, so we can offer a degree of insight into the functions of Opera for handhelds. In this article, we've prepared a set of general suggestions for creating a handheld-friendly style sheet, along with a few Opera-specific pointers that you may find useful.

Too often, when companies decide to make a mobile version of their application, they take their desktop application or site, decide which features work for mobile, and then convert those features to a mobile language or two. Through this method we get flight times, stock prices, checking email, checking calendars, local weather, and several other useful but limited applications. These applications do not fully meet user needs. To do anything in particular, the user has to visit several applications, one after the other, remembering data from application to application.

The Palm Pre smart phone and the company's much-anticipated new operating system-called webOS-are among the most buzzed-about products to come out of CES this year. Despite staging its splashy launch, Palm has been a bit secretive with the device-reminding us of a certain company in Cupertino. But PC World had the chance to sit down with the company and delve into the OS everyone is talking about. And though we had very limited time with the Pre and WebOS, we can tell you what we liked-and what we didn't.

I've seen many prototypes of mobile UIs that can't be built and if they could, would not be legible on a small LCD screen. So I thought I'd provide some pointers that might help those of you that is starting out. Often, people starting out prototyping mobile phone UIs get the size of the display right but the size of the font wrong. They try to stuff way too much in there, and they use a font size and font family that is not available in the phone.

There is good news and surprising report as well that Samsung is planning to offer freemium games to the owners of Galaxy S7 and Galaxy S7 Edge. The company is trying to encourage their customers by offering a lot of freebies to those patrons who hold the flagship smartphones

The mobile web is here to stay -- but is your site optimized for users that are on the run? In this article, Brian reveals seven fundamental tips to make sure your web site is a joy to use for all users -- including those browsing from a mobile phone.