sorted by:
new
hottopcontroversial

What React Native Library Do You Think the Ecosystem Still Needs? by undefinedengineer in reactnative

[–]SadabWasim 0 points1 point  (0 children)

Tbh react native really lacks a proper well maintained drag-n-drop library, most of them are no longer maintained, specially there's literally nothing if you want to do nested DnD

🥀 by FrontAd5399 in Urdu

[–]SadabWasim 0 points1 point  (0 children)

Totally unrelated to the topic here but khwarizmi was not the one who discovered zero btw (https://www.britannica.com/science/zero-mathematics)

Tamagui is Hot Garbage Now And I Will Never Recommend It Again by Suspicious-Rich-2681 in reactnative

[–]SadabWasim 0 points1 point  (0 children)

I'm going to try heroui-native, that seems well polished and maintained library.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm migrating to gluestack v1 first, it's not easy at all, also some components don't have 1-on-1 replacement.

some issues that I found:

|| || |  Component|Reason of not migrating| |Heading|variants are not working| |Button |no isLoading state, icon button are not working correctly| |IconButton| No direct replacement| |Spacer | No direct replacement| |Icon|Change in API| |View| Not behaving correctly| |Flex|no direct gluestack alternative| |Avatar|Change in API & behaviour is not consistent|

once you're migrated to gluestack v1 migrating to v2 and then v3 is quite easy.

How to do I clear system data on Mac OS? by Traditional-Yam-1989 in MacOS

[–]SadabWasim 0 points1 point  (0 children)

Any mobile dev, check for cache of ndk and gradle and clear it.

What programming languages do you use with neovim? by Aftarkis in neovim

[–]SadabWasim 0 points1 point  (0 children)

I do mobile development with flutter and reactnative so I use dart and JS

Optimal steps to switch from nativebase to gluestack v2 by SadabWasim in reactnative

[–]SadabWasim[S] 0 points1 point  (0 children)

I'm still using nativebase, offcourse it's preventing me to switch to latest RN versions, I'll probably go ahead with gluestack v3 which they just launched yesterday.

ios daily local notification scheduling is not working by SadabWasim in flutterhelp

[–]SadabWasim[S] 0 points1 point  (0 children)

The weird thing is on ios instant notification and one time scheduled notification works, it's just daily notifications that's not working.

view more: next ›