Checkout this question on Stackoverflow: http://stackoverflow.com/questions/27477371/android-elevation-not-showing-a-shadow

cc @janicduplessis @satya164

How about add a new style property such as outlineProvider (https://developer.android.com/reference/android/view/ViewOutlineProvider.html), just like what we did in Libraries/Components/View/ViewStylePropTypes.js

  /**
   * (Android-only) Sets the elevation of a view, using Android's underlying
   * [elevation API](https://developer.android.com/training/material/shadows-clipping.html#Elevation).
   * This adds a drop shadow to the item and affects z-order for overlapping views.
   * Only supported on Android 5.0+, has no effect on earlier versions.
   * @platform android
   */
  elevation: ReactPropTypes.number,

  outlineProvider: ReactPropTypes.oneOf(['bounds', 'padded_bounds', 'background'])

<View style={{elevation: 10, outlineProvider: 'bounds'}}
  ...
</View>

Looks bad

<View style={{alignItems: 'center', marginTop: 50, elevation: 10, outlineProvider: 'bounds'}}>
  <Text>Hello World</Text>
</View>

@niagr I have implemented CardView for react-native with elevation, that support android(All version) and iOS. Let me know is it help you or not. https://github.com/Kishanjvaghela/react-native-cardview

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.