Android app version in layout

How to set app’s version number in Android Studio

I would like to upgrade an app’s version number (that is displayed in the Play Store) in Android Studio, but I’m not an Android developer so I’m not sure what I’m doing is right. I googled how to do it, and the Android guide says I should have to do it in the AndroidManifest.xml , but I can’t find android:versionCode , android:versionName in that file. However I found these lines in the build.gradle :

The actual version number is 1.1 in the Play Store, so I assume I got this, but I would really appreciate if somebody could confirm it for me. So is it enough if I edit only the versionName in the build.gradle ? Or do I need to do anything else? What is the common practice to do this?

2 Answers 2

Yes, every time you release an update on PlayStore you need to update these two lines in your gradle file by incrementing the digits in front of them —

Your versionCode should always be incremented but versionName is totally up to you when you plan to release an update. I usually increment my versionName based on how big is the update that I’m releasing.

If its a huge update to the previous version like new UI OR too many new features then I increment versionName by 1 and change it to 2.0, 2.1 etc

If its a small one, for instance I fixed few bugs then I usually increment versionName to 1.1.1, 1.1.2 etc.

If its just one new feature or I changed some vital content in my app then I increment the versionName to 1.2, 1.3 etc.

For ex. Minimum increment from versionCode 1 and versionName 1.1 can be —

You can find more info here — Versioning an Android app. Just keep in mind this document still explain versioning using AndroidManifest which still works but not recommended anymore as the values will be overridden by values in gradle file.

NOTE

As CommonsWare mentioned in his comment, you can change your versionCode to be something meaningful like date or anything that makes more sense to you. Play store will not raise any issue till the time its an integer and the newer one is higher than the older one.

Источник

Основы верстки для нативных андроид приложений

( пользоваться не рекомендуется, deprecated )
AbsoluteLayout — означает что каждый элемент верстки будет иметь абсолютную позицию относительно верхнего левого угла экрана задаваемую с помощью координат x и y. Т.е. верхнийлевый угол экрана при AbsoluteLayout имеет координаты x = 0, y = 0.
Позиция указывается в атрибутах элемента android:layout_x и android:layout_y.
Пример кода:

FrameLayout

FrameLayout — тип верстки внутри которого может отображаться только один элемент в строке. Т.е. если внутри FrameLayout вы поместите несколько элементов, то следующий будет отображаться поверх предыдущего.
Пример кода:

LinearLayout

LinearLayout — тип верстки при котором область верстки делится на строки и в каждую строку помещается один элемент. Разбиение может быть вертикальное или горизонтальное, тип разбиения указывается в атрибуте LinearLayout android:orientation. Внутри верстки возможно комбинировать вертикальную и горизонтальную разбивки, а кроме того, возможна комбинация нескольких разных типов верстки например использование LinearLayout внутри FrameLayout.

Пример вертикальной разбивки LinearLayout:

Пример горизонтальной разбивки LinearLayout:

Комбинация нескольких LinearLayout:

RelativeLayout

RelativeLayout — тип верстки при котором позиционирование элементов происходит относительно друг друга и относительно главного контейнера.
За то, каким образом будут позиционироваться элементы отвечают следующие атрибуты:
Атрибуты позиционирования относительно контейнера

• android:layout_alignParentBottom – Низ элемента находится внизу контейнера
• android:layout_alignParentLeft – Левая часть элемента прилегает к левой части контейнера
• android:layout_alignParentRight – Правая часть элемента прилегает к правой части контейнера
• android:layout_alignParentTop – Элемент находится в верхней части контейнера
• android:layout_centerHorizontal – Элемент позиционируется по центру относительно горизонтального размера контейнера
• android:layout_centerInParent – Элемент позиционируется по центру относительно горизонтального и вертикального размеров размера контейнера
• android:layout_centerVertical – Элемент позиционируется по центру относительно вертикального размера контейнера

Атрибуты позиционирования относительно других элементов.
В качестве значений этих атрибутов ставятся id элемента относительно которого будет производится позиционирование.

android:layout_above – Распологает элемент над указанным
android:layout_below – Распологает элемент под указанным
android:layout_toLeftOf – Распологает элемент слева от указанного
android:layout_toRightOf – Распологает элемент справа от указанного

Выравнивание относительно других элементов.

android:layout_alignBaseline – Выравнивает baseline элемента с baseline указаннго элемента
android:layout_alignBottom – Выравнивает низ элемента по низу указанного элемента
android:layout_alignLeft – Выравнивает левый край элемента с левым краем указанного элемента
android:layout_alignRight – Выравнивает правый край элемента с правым краем указанного элемента
android:layout_alignTop – Выравнивает верхнюю часть элемента в соответствие с верхней частью указанного элемента

TableLayout

TableLayout — табличная верстка.
Организует элементы в строки и столбцы таблицы.
Для организации строк служит таг

Alternate Layouts

Alternate Layouts — альтернативная верстка. Позволяет использовать различную верстку для различных ориентаций экрана.
XML для альтернативной верстки помещается в папки проекта:

res/layout-land – альтернативная верстка для landscape UI
res/layout-port –альтернативная верстка для portrait UI
res/lauout-square – альтернативная верстка для square UI

и перед тем как получить макет из res/lauout система проверяет наличие файлов в этих папках.

И в завершении немного о стилях.

Стили

Во первых стили элемента могут быть описаны в атрибутах самого элемента.
Например:

Кроме того стили можно вынести в отдельный xml файл и сохранить его в папке res/values/
Напимер:

Если мы вынесем стили в отдельный файл, то для описания стилей элемента будем использовать атрибут style.

Источник

Android — Layout File (XML)

Table of Contents

About

A layout XML is a declarative way of creating an UI.

To define the GUI in android, you can do it:

The XML vocabulary maps to the subclasses of ViewGroup (UI container) and View (widgets) .

The advantage to declaring your UI in XML is that:

Articles Related

Syntax

Each layout file must contain:

The XML attribute reference can be found in the API References

160 DPI 1x HDPI

240 DPI 1,5x XHDPI

320 DPI 2x XXHDPI

Example

Linear

Data-binding layout

Data-binding layout files are slightly different and start with a root tag of layout followed by a data element and a view root element.

Location

Default

All XML layout file are saved in the following directory:

Multiple Screens support

Directories

Layout file decision

The layout are chosen in a cascade way. For instance, with this directory structure:

The following layout file will be chosen:

Application is running on	Height	Width	Smallest Width (sw)	main.xml Directory	detail.xml directory	item.xml directory
Nexus 5	640 dp	360 dp	360 dp	res/layout	res/detail.xml	res/item.xml
Nexus 7	960 dp	600 dp	600 dp	res/layout	res/layout-sw600dp/detail.xml	res/layout-sw600dp/item.xml
Nexus 10	800 dp	1280 dp	800 dp	res/layout	res/layout-sw600dp/detail.xml	res/layout-sw720dp/item.xml

Alias

The smallest-width qualifier is available only on Android 3.2 and above. Therefore, you should also still use the abstract size bins (small, normal, large and xlarge) to be compatible with earlier versions. See Layout Aliases

You can use refs.xml for your alias because it’a a more descriptive name thant layout.xml

Built-in

Android has standard layout. They all begins with android.R.layout . See android/R.layout

Load the XML Layout

To use the layout XML, you inflate it from an activity. See Android — Inflate (a layout XML to a view UI object).

Attribute Namespace

App Attributes are custom attributes defined in your app, whether by your code or by libraries you import.

It’s a single global namespace for custom attributes — i.e., attributes not defined by the android system.

App attributes that don’t exist are silently ignored.

For instance, the appcompat-v7 library uses this app custom attributes mirroring the android: namespace ones to support all prior versions of android.

Android

The android namespace are attribute defined by the android system.

Tools

the tools namespace that enable design-time features (such as which layout to show in a fragment) or compile-time behaviors (such as which shrinking mode to apply to your XML resources).

Источник

Android Layout — when to use app: vs android:?

I’ve been writing some Android apps but I don’t really understand when to use app: and when to use android: . When styles are not being applied the way they’re supposed to, I use trial and error and sometimes find that using app: instead of android: solves the issue but I don’t understand why. It’d be great if someone could point me in the right direction. Thanks!

5 Answers 5

You can use the app namespace to have app compatibility with older API versions.

For example app:srcCompat=»@drawable/customborder» has the same effects with android:background=»@drawable/customborder» The difference is that the first will work correctly with older API’s and the second will not display what you would like.

You are talking about custom namespace.In android we can create custom views in additional to already available views. As per in Google developer docs.. To add a built-in View to your user interface, you specify it in an XML element and control its appearance and behavior with element attributes. Well-written custom views can also be added and styled via XML. To enable this behavior in your custom view, you must:

Define custom attributes for your view in a resource element Specify values for the attributes in your XML layout Retrieve attribute values at runtime Apply the retrieved attribute values to your view

Once you define the custom attributes, you can use them in layout XML files just like built-in attributes. The only difference is that your custom attributes belong to a different namespace. Instead of belonging to the http://schemas.android.com/apk/res/android namespace, they belong to http://schemas.android.com/apk/res/[your package name]

So for if you use default views you can use android namespace and if you want to set and use attributes for custom view you can define your own name.

Источник

Basics of Android layouts and views

What is a ViewGroup?

A viewgroup is a parent class of all the views. It holds all the children views (and viewgroups) within, as depicted by the structure above.

Types of ViewGroups

• Absolute Layout
• By using an Absolute Layout, you can specify the exact locations (x/y coordinates) of its children.
• They are less flexible and harder to maintain, rarely used nowadays.
• One needs to remember too many coordinate values for placing a view at a position, it would rather be much easier to remember a view with respect to which one needs to place a view on screen.

• It is usually used to block out an area on the screen and display only a single child on screen.
• If multiple children are used within it then all the children are placed on top of each other.
• Position of children can only be controlled by assigning gravity to them.
• Usually used to display single fragments on screen.

• Aligns the children views either horizontally or vertically.
• The attribute android:orientation specifies wheher to horizontally or vertically align children views.
• We usually use the attribute android:weight in the children views/viewgroups to decide what percentage of the available space they should occupy.
• An attribute android:weightSum defines the maximum weight sum, and is calculated as the sum of the layout_weight of all the children if not specified explicitly.

TRIVIA : What would happen if the weightSum is less than the sum of weights given to children explicitly?

• Relative Layout enables you to specify how child views are positioned relative to each other.
• The position of each view can be specified as relative to sibling elements or relative to the parent.

Some common attribute usages in relative layout:
Difference between android:layout_alignRight and android:layout_toRightOf : android:layout_alignRight is used to align a view’s rightmost edge to the rightmost edge of the specified view, whereas android:layout_toRightOf is used to place a view to the right of the specified view ie the left edge of a view is postioned to the right of the specified view.

Why to prefer android:layout_toEndOf instead of android:layout_toRightOf :
The views have LTR(left-to-right) orientation by default ie they start from left and end towards their righ, butthis orientation can be changed to RTL(right-to-left) where views start from right and end towards left. In suchcses,the views with the attribute android:layout_toEndOf will correctly align to the end w.r.t the view specifiedwhereas android:layout_toRightOf will still align it towards the right.

• Read more about Relative Layout here and here.

TRIVIA: Relative Layout measures a view twice, whereas Linear Layout measures only once (if weights are not used)!
Sources: Stack Overflow and Medium

• Instead of specifying the width and height of a child, we can provide a percentage of screen width or height to use.
• It is very useful in scaling layouts to various screen sizes.
• The PercentSupportLayout supports two pre-built layout — PercentRelativeLayout and PercentFrameLayout .
• Find an example for this here.
• ScrollView
• It is a subclass of FrameLayout, as the name says it is used when your contents do not fit the screen and tend to overflow.
• ScrollView can hold only one direct child. This means that you need to wrap all your views into a single viewgroup in order to use it within a ScrollView.
• ScrollView only supports vertical scrolling. Use HorizontalScrollView if you want to have horizontal scrolling.
• It is advised not to use ScrollView with ListView , GridView and Recycler View as they take care of their own vertical scrolling.

Источник