CardView with Material Design using ConstraintLayout
Switch branches/tags
Nothing to show
Clone or download
Latest commit a89cc9f Apr 17, 2018

README.md

CardView with Material Design using ConstraintLayout

This sample contains the layout implementation for all the possible CardView combinations listed in Material design guidelines - Content block combinations.

Introduction

Material design guidelines mention that cards can be constructed using blocks of content which include:

  • An optional header
  • A primary title
  • Rich media
  • Supporting text
  • Actions

These blocks can be organized to promote different types of content.

This sample implements layouts for all the possible CardView combinations listed in Material design guidelines - Content block combinations. All the layouts implemented with using ConstraintLayout.

Pre-requisites

  • Android Studio 3.+
  • Gradle 3.+

Screenshots

A screenshot illustratrating the UI of the app

Getting started

Check out branch master and then open the android-cards/ directory in Android Studio.

Support

If you've found an error in this sample, please file an issue: https://github.com/eugenebrusov/android-cards/issues

License

Copyright (c) 2017 Eugene Brusov

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.