Post 1083193 by unstuckdev@mastodon.social
 (DIR) More posts by unstuckdev@mastodon.social
 (DIR) Post #1083114 by baldur@toot.cafe
       2018-11-09T19:15:30Z
       
       0 likes, 0 repeats
       
       “React Native Accessibility Is Pretty Bad”A common reason for using frameworks in native and web apps is to save time and money. Those savings tend to mostly come from not making the project accessible. http://www.takingnotes.co/blog/2018/11/09/react-native-accessibility/
       
 (DIR) Post #1083115 by baldur@toot.cafe
       2018-11-09T19:15:31Z
       
       0 likes, 0 repeats
       
       Once you factor in the cost of making the project accessible and performant, you often end up spending as much time and money as you would have without a framework.
       
 (DIR) Post #1083171 by baldur@toot.cafe
       2018-11-09T19:19:17Z
       
       0 likes, 0 repeats
       
       Which isn't to say you should avoid using frameworks. Just that you should use one when it enables you to things that would have been impossible for you otherwise.
       
 (DIR) Post #1083193 by unstuckdev@mastodon.social
       2018-11-09T19:20:16Z
       
       0 likes, 0 repeats
       
       @baldur Software development seems to be a cascade of catch-22s.
       
 (DIR) Post #1083205 by baldur@toot.cafe
       2018-11-09T19:21:19Z
       
       0 likes, 0 repeats
       
       @unstuckdev Yeah. Pretty much.