ホーム > Uncategorized > Public bookmarks 10/03/2013 (p.m.)

Public bookmarks 10/03/2013 (p.m.)


    • First you can use the Open Source project  ActionBar Sherlock  which  allows you  to use the ActionBar on Android  devices  as of Android  1.6.  You find  this library under the following link.   

       

         

      http://actionbarsherlock.com 
    • The second option is to use the ActionBarCompat library from the  Android support library v7, which supports the action bar as of  Andriod 2.1.
    • Changing the hostname on CentOS
    • HOSTNAME="ftp.example.com" 

        

    • $ hostname ftp.example.com

        

    • 127.0.0.1  ftp.example.com localhost localhost.localdomain

       <!– google_ad_section_end –>  

        

    • Amazon Linux AMI

        

       
       
        

      The Amazon Linux AMI is a supported and maintained Linux image provided by Amazon Web Services for use on Amazon Elastic Compute Cloud (Amazon EC2). It is designed to provide a stable, secure, and high performance execution environment for applications running on Amazon EC2. It also includes packages that enable easy integration with AWS, including launch configuration tools and many popular AWS libraries and tools. Amazon Web Services provides ongoing security and maintenance updates to all instances running the Amazon Linux AMI. The Amazon Linux AMI is provided at no additional charge to Amazon EC2 users.

    • Tabs should be persistent across immediate related screens
    • tab switches should not be treated as history
    • tabs should always run along the top of the screen
    • customize tab indicators, showing text and/or icons to make optimal use of vertical space
    • list of screens that covers these use cases.
    • Putting it All Together: Wireframing the Example App
    • Don’t use bottom tab bars

       

      Other platforms use the bottom tab bar to switch between the app’s views. Per platform convention, Android’s tabs for view control are shown in action bars at the top of the screen instead. In addition, Android apps may use a bottom bar to display actions on a split action bar.

    • Don’t hardcode links to other apps

       

      In some cases you might want your app to take advantage of another app’s feature set. For example, you may want to share the content that your app created via a social network or messaging app, or view the content of a weblink in a browser. Don’t use hard-coded, explicit links to particular apps to achieve this. Instead, use Android’s intent API to launch an activity chooser which lists all applications that are set up to handle the particular request. This lets the user complete the task with their preferred app. For sharing in particular, consider using the Share Action Provider in your action bar to provide faster access to the user’s most recently used sharing target.

    • Don’t use right-pointing carets on line items
      • Writing Style

           

           

           

               

           
         

        When choosing words for your app:

         

           
        1.  

          Keep it brief. Be concise, simple and precise. Start with a 30 character limit (including  spaces), and don’t use more unless absolutely necessary.

           

        2.  

        3.  

          Keep it simple. Pretend you’re speaking to someone who’s smart and competent, but doesn’t  know technical jargon and may not speak English very well. Use short words, active verbs, and  common nouns.

           

        4.  

        5.  

          Be friendly. Use contractions. Talk directly to the reader using second person (“you”). If  your text doesn’t read the way you’d say it in casual conversation, it’s probably not the way  you should write it. Don’t be abrupt or annoying and make the user feel safe, happy and  energized.

           

        6.  

        7.  

          Put the most important thing first. The first two words (around 11 characters, including  spaces) should include at least a taste of the most important information in the string. If they  don’t, start over.

           

        8.  

        9.  

          Describe only what’s necessary, and no more. Don’t try to explain subtle differences. They  will be lost on most users.

           

        10.  

        11.  

          Avoid repetition. If a significant term gets repeated within a screen or block of text, find  a way to use it just once.

    • Launcher icons on a mobile device must be 48×48 dp.
    • Remove unnecessary metadata from final assets

        

      Although the Android SDK tools will automatically compress PNGs when packaging application resources into the application binary, a good practice is to remove unnecessary headers and metadata from your PNG assets. Tools such as OptiPNG or Pngcrush can ensure that this metadata is removed and that your image asset file sizes are optimized.

    • Why 48dp?

       

      On average, 48dp translate to a physical size of about 9mm (with some variability). This is comfortably in the range of recommended target sizes (7-10 mm) for touchscreen objects and users will be able to reliably and accurately target them with their fingers.

    • Most of Android’s UI elements have touch-feedback built in, including states that indicate  whether touching the element will have any effect.
      • A typical Android app consists of action bars and the app content area.

         

           
        1.  

          Main Action Bar

           

          The command and control center for your app. The main action bar includes elements for  navigating your app’s hierarchy and views, and also surfaces the most important actions.

           

          More on the Action Bar

           

        2.  

        3.  

          View Control

           

          Allows users to switch between the different views that your app provides. Views typically  consist of different arrangements of your data or different functional aspects of your app.

           

        4.  

        5.  

          Content Area

           

          The space where the content of your app is displayed.

           

        6.  

        7.  

          Split Action Bar

           

          Split action bars provide a way to distribute actions across additional bars located below  the main action bar or at the bottom of the screen. In this example, a split action bar moves  important actions that won’t fit in the main bar to the bottom.

    • Fixed Tabs


       

      Fixed tabs display all items concurrently. To navigate to a different view, touch the tab, or swipe left or right.

       

      Fixed tabs are displayed with equal width, based on the width of the widest tab label. If there is insufficient room to display all tabs, the tab labels themselves will be scrollable. For this reason, fixed tabs are best suited for displaying 3 or fewer tabs.

    • Applications often include settings that allow users to modify app features and behaviors. For example, some apps allow users to specify whether notifications are enabled or specify how often the application syncs data with the cloud.

        

    • The action bar is a window feature that identifies the user location, and provides user actions and navigation modes. Using the action bar offers your users a familiar interface across applications that the system gracefully adapts for different screen configurations.
      • The action bar provides several key functions:

          

           
        • Provides a dedicated space for giving your app an identity and indicating the user’s  location in the app.
        •  

        • Makes important actions prominent and accessible in a predictable way  (such as Search).
        •  

        • Supports consistent navigation and view switching within apps (with tabs or drop-down  lists).
    • Using split action bar

        

      Split action bar provides a separate bar at the bottom of the screen to display all action items when the activity is running on a narrow screen (such as a portrait-oriented handset).

    • Adding Navigation Tabs
    • Tabs in the action bar make it easy for users to explore and switch between different views in your app. The tabs provided by the ActionBar are ideal because they adapt to different screen sizes. For example, when the screen is wide enough the tabs appear in the action bar alongside the action buttons (such as when on a tablet, shown in figure 7), while when on a narrow screen they appear in a separate bar (known as the “stacked action bar”, shown in figure 8). In some cases, the Android system will instead show your tab items as a drop-down list to ensure the best fit in the action bar.
  • tags: android navigation

Posted from Diigo. The rest of my favorite links are here.

カテゴリー:Uncategorized
  1. まだコメントはありません。
  1. No trackbacks yet.

コメントを残す

以下に詳細を記入するか、アイコンをクリックしてログインしてください。

WordPress.com ロゴ

WordPress.com アカウントを使ってコメントしています。 ログアウト / 変更 )

Twitter 画像

Twitter アカウントを使ってコメントしています。 ログアウト / 変更 )

Facebook の写真

Facebook アカウントを使ってコメントしています。 ログアウト / 変更 )

Google+ フォト

Google+ アカウントを使ってコメントしています。 ログアウト / 変更 )

%s と連携中

%d人のブロガーが「いいね」をつけました。