Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4343652
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T11:47:02+00:00 2026-05-21T11:47:02+00:00

Understand that 1×1 widget size should be 72 dip x 72 dip, but this

  • 0

Understand that 1×1 widget size should be 72 dip x 72 dip, but this is seems to be less than standard icon size. If I change size to 80 dip x 80 dip, then it looks as the same. Is it OK if I would use this size?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-21T11:47:03+00:00Added an answer on May 21, 2026 at 11:47 am

    Quoting the documentation:

    The default Home screen positions App
    Widgets in its window based on a grid
    of cells that have a defined height
    and width. If the values for an App
    Widget’s minimum width or height don’t
    match the dimensions of the cells,
    then the App Widget dimensions round
    up to the nearest cell size. (See the
    App Widget Design Guidelines for more
    information on the Home screen cell
    sizes.)

    Because the Home screen’s layout
    orientation (and thus, the cell sizes)
    can change, as a rule of thumb, you
    should assume the worst-case cell size
    of 74 pixels for the height and width
    of a cell. However, you must subtract
    2 from the final dimension to account
    for any integer rounding errors that
    occur in the pixel count.

    Those instructions are for “the default Home screen”. Other home screen implementations may behave differently. If your widget layout and such will work well both at the regular size and your slightly larger size, in principle your 80dip will work — just understand that your request for 8dip of additional space will typically be ignored.

    Personally, I would use 72dip, to ensure compatibility.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I understand that they are both supposed to be small, but what are the
I understand that Microsoft uses this template when versioning their products: Major.Minor.Build.Revision. Major is
I understand that requests are served by different threads, but do they all come
I understand that this response clearly states that this is not possible without a
I understand that loops are a bad idea in python and I should avoid
I understand that SimpleXML is far more efficient than DOMDocument. Any advice on how
I understand that the CLR needs to do marshaling in some cases, but let's
I understand that 0MQ is supposed to be faster than TCP Sockets in a
I understand that in Ruby running on YARV, threads mean concurrency rather than parallelism.
I understand that t:saveState allows a request scope bean to persist for longer than

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.