No, React Native is not the future

Mobile Apps Arcade App Store

F-Droid Landing Page

1

F-Droid

F-Droid is an interesting alternative for Android users who want to try something different and not have to use the Goole Play store all the time.

#App Store #Mobile Apps #Software Marketplace 375 social mentions
40 Hadiths Landing Page
2

40 Hadiths

Hadith Nawawi is an Islamic Android App that is designed with the purpose to enlighten the heart and souls of Muslims around the globe with the authentic teachings of Prophet Muhammad (PBUH).
Pricing:
- Open Source
Interesting tech. Looks like it's developed by hey.com, and their email app on Google Play store is only 9MB, which is impressive. From what sparse commentary I could find online, looks like this is a middle ground between web dev and native dev. It allows reusing server logic to emit html markup for mobile UI, but requires platform developers to put in the necessary native pieces piecemeal (sensible choice considering the leaky abstractions in react native). <a href="https://play.google.com/store/apps/details?id=com.basecamp.hey">https://play.google.com/store/apps/details?id=com.basecamp.h...</a>.

#Mobile Apps #Religion #Web Search 1164 social mentions
Radiant Landing Page
3

Radiant

Radio hosted by an AI presenter
Pricing:
- Open Source
Having read through the comments and tried standard notes I can see why users might have been disappointed going from native to this web implementation. I recently went through the process of switching to a web stack from a native iOS stack when it came time to support Android with one of my apps (https://getradiant.app/) and my biggest concern was making it feel a near as possible to the native app it was replacing and having it perform as well as possible on older Android devices. It turned out quite well and I’ve never had a user complain about the transition. The trick to my mind was to treat web dev like mobile dev. Focus on bundle size, load speed and fluidity within the confines of a mobile environment. Constantly compare what you’re building to a native app. Probably focus on SPA over SSR/MPAs. And remember, if you apply all of the above to much less restrictive desktop browser environment with a much performance ceiling, the experience is going to be pretty good. TLDR; think small, think fast and start with the most constrained environment you’re targeting, usually mobile, usually older Android. If you understand the limitations and considerations of browser engines when taking into account the above, the rest will follow and you’re going to have a good time.

#Arcade #Action #Music 31 social mentions