Technetium Blog

  This article will offer a list of suggestions for optimizing performance while building a React Native app 1. Avoid use inline functions directly as props to a component & also avoid inline styling  class Foo extends Component { render ( ) { return ( < button onClick = { ( ) => console . log ( 'boop' ) } > { /* 🙅‍♀️ */ } BOOP </ button > ) ; } } class Foo extends Component { handleClick = ( ) => { // this anonymous function is fine used like this console . log ( 'boop' ) ; } render ( ) { return ( < button onClick = { this . handleClick } > { /* 🙆‍♂️ */ } BOOP </ button > ) ; } } onPress contains an arrow function , a new reference to that inline function is declared in every render . It is not recommended that way. Causing an unnecessary re-render computation. use StyleSheet for styles ref https://medium.com/corebuild-so

Miracast  Miracast works completely offline Part of the Wi-Fi features on new (gadgets/SmartTV)/dongle Uses Wi-Fi Direct(two devices connect to each other wirelessly, without a Wi-Fi router) Chances are, if you bought a gadget after 2014, it will support Miracast. This includes most TVs, who disguise their Miracast feature under names like "SmartShare", "AllShare", and so on Which Android devices support Miracast? Android supported Miracast in Android 4.2 (KitKat) and Android 5 (Lollipop). However, Google dropped native Miracast support in Android 6 (Marshmallow) and later.  Workaround solution (not tested) Use 3rd party app ay playstore but contain ads at setup( not sure ads will popup while using or not) Google home application Tech https://youtu.be/DhQ3VLesDHM   (miracast dongle for iphone old tv) https://www.youtube.com/watch?v=TCJEGy8ylrk  (miracast dongle for android old tv)         Workaround (miracast dongle for not support android old tv) https://www.youtu

*This article covers the Skeleton Screen Packages in React Native options crafted to encourage usability. A skeleton UI resembles the page’s actual UI, so users will understand how quickly the mobile app will load even before the content has shown up. Here are the skeleton screens packages you might want to consider using in your next project: Skeleton Screen Packages in React Native rn-placeholder react-native-skeleton-content-nonexpo rn-placeholder Style Make use of it as component  Props Animation Fade Loader Progressive Raw Shine ShineOverlay Props PlaceholderMedia = image placeholder PlaceholderLine = text placeholder Example import   {   Placeholder ,   PlaceholderMedia ,   PlaceholderLine ,   Fade }   from   " rn-placeholder " ;   const   App   =   ( )   =>   (    <Placeholder Animation={Fade} style={{ marginVertical: 6, marginHorizontal: 15, borderRadius: 4, }} Left={props => ( <PlaceholderMedia style={[

  Skeleton Screens UI and UX experts said that while users wait for content to load on a page, users should be engaged with the loading page. The idea behind using spinners to engage users before content loads is great; however, the result can be less than ideal because most users will get bored or no sign of progress staring at a dummy animated spinner like it’s a clock A skeleton screen is essentially a wireframe of the application. The wireframe is a placeholder until the application finally loads. The skeleton loading screen essentially impersonates the original layout. Rather than most performance or UX wins, this pattern only focuses on improving the perceived experience. When compared against a blank screen or a traditional spinner, skeleton screens are seen as shorter in duration Benefits of Skeleton Screens in Apps 1. Increase perceived performance App feel faster,  App feel more responsive App feel more user friendly. 2. Reduce surprise and disorientation as content loads Use