create-expo-cljs-app
Version:
Create a react native application with Expo and Shadow-CLJS!
108 lines (98 loc) • 4.22 kB
JavaScript
/**
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*
* @format
* @flow
*/
;
const React = require('react');
const {StyleSheet, View, Text, Button, Share} = require('react-native');
const shareMessage = () => {
Share.share({
message: ('Our top priority for React Native is to match the expectations people have for each platform. This is why React Native renders to platform primitives. We value native look-and-feel over cross-platform consistency.' +
'For example, the TextInput in React Native renders to a UITextField on iOS. This ensures that integration with password managers and keyboard controls work out of the box. By using platform primitives, React Native apps are also able to stay up-to-date with design and behavior changes from new releases of Android and iOS.': string),
});
};
const shareText = () => {
Share.share(
{
title: 'Massive Scale',
message: ('Hundreds of screens in the Facebook app are implemented with React Native. The Facebook app is used by billions of people on a huge range of devices. This is why we invest in the most challenging problems at scale.' +
'Deploying React Native in our apps lets us identify problems that we wouldn’t see at a smaller scale. For example, Facebook focuses on improving performance across a broad spectrum of devices from the newest iPhone to many older generations of Android devices. This focus informs our architecture projects such as Hermes, Fabric, and TurboModules.': string),
url: 'https://reactnative.dev/blog/2020/07/17/react-native-principles',
},
{
subject: 'MUST READ: Massive Scale',
dialogTitle: 'Share React Native Blog',
excludedActivityTypes: ['com.apple.UIKit.activity.PostToTwitter'],
tintColor: 'blue',
},
);
};
const ShareMessageWithoutTitle = () => {
return (
<View style={styles.container}>
<Text style={styles.title}>Native Experience</Text>
<Text>
Our top priority for React Native is to match the expectations people
have for each platform. This is why React Native renders to platform
primitives. We value native look-and-feel over cross-platform
consistency. For example, the TextInput in React Native renders to a
UITextField on iOS. This ensures that integration with password managers
and keyboard controls work out of the box. By using platform primitives,
React Native apps are also able to stay up-to-date with design and
behavior changes from new releases of Android and iOS.
</Text>
<Button title="SHARE" onPress={shareMessage} />
</View>
);
};
const ShareMessageWithTitle = () => {
return (
<View style={styles.container}>
<Text style={styles.title}>Massive Scale</Text>
<Text>
Hundreds of screens in the Facebook app are implemented with React
Native. The Facebook app is used by billions of people on a huge range
of devices. This is why we invest in the most challenging problems at
scale. Deploying React Native in our apps lets us identify problems that
we wouldn’t see at a smaller scale. For example, Facebook focuses on
improving performance across a broad spectrum of devices from the newest
iPhone to many older generations of Android devices. This focus informs
our architecture projects such as Hermes, Fabric, and TurboModules.
</Text>
<Button title="SHARE" onPress={shareText} />
</View>
);
};
const styles = StyleSheet.create({
container: {
flex: 1,
alignItems: 'center',
justifyContent: 'center',
},
title: {
fontSize: 30,
margin: 10,
textAlign: 'center',
},
});
exports.title = 'Share';
exports.description = 'Share data with other Apps.';
exports.examples = [
{
title: 'Share message',
render(): React.Node {
return <ShareMessageWithoutTitle />;
},
},
{
title: 'Share message, URL (iOS) and title (Android)',
render(): React.Node {
return <ShareMessageWithTitle />;
},
},
];