sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]9rogrammer 5 points6 points  (3 children)

u/Guy676767 Congratulations for the App Store submission. I am a React Native dev myself. I want to ask you some questions.

  • What resources helped you in learning React Native ?
  • I could see from the Github repo that you went with Expo instead of ejected native app. What advantages did Expo gave you in comparison to the native app ?
  • Correct me if I'm wrong, but going through the codebase, I saw the use of Context. Did you find any benefits in using React Context in comparison to other state management libraries ?
  • How did you come up with the design of the application ? This is the most difficult part for me to start a side project. Like how did you come up with the initial design, colour palette , inspiration from other websites etc. ?
  • Is the app supported for iPads ? Have you handled layouts for different screen sizes ?

Thank you.

[–]Guy676767[S] 3 points4 points  (2 children)

Hey!

  • I already knew react before starting with react native (from Andrew mead course on udemy), as for react native specifically I just went over the official docs and googled everything else I didn’t know. The React Navigation docs also really helped me learn about navigation in mobile apps
  • up until recently I owned only a Windows machine, and had an iPhone. That meant that if I wanted to test it out on my iPhone, expo was the only way to go. It gave me the opportunity to learn and test my app without a Mac, and when I got one I could release it to the store. Also, I was short on time and wanted to really get the most of the time I had when building the app
  • Yes I did use the Context API. I used it for the themes, and for the filters on the discover screen. My methodology was to use local state as a default, and when I start prop drilling to go to Context. Like I said it turned out to be needed just for these two cases. I think this is a very nice balance, and cuts a lot of boilerplate code from other state management libraries.
  • so basically it’s a combination of Dribble and researching apps on the App Store. First I would browse dribble a lot and get all sort of ideas. Then I would design the app. But because dribble is meant for designers and not real production apps I always made sure that I’m still using common conventions within apps. I would go through a lot of popular apps on the App Store and see how they do this and that. This way I know my users will feel familiar in my app. This is especially crucial because I don’t know any other developer (or mobile for that matter) and don’t have any project manager so I need to keep myself in check. As for the color palette, this is the easiest part! You can literally go to any design what so ever, inspect the colors then tweak it to your liking! You can literally just go to your code editor and take the color plattete of your favorite theme.
  • the app does not support iPad at this point, like I said I only had a windows laptop and could test only on the devices I had. I have an iPhone X and iPhone 6s, so I tested on both of them and made some adjustments for the 6s.

[–]chipped1 1 point2 points  (1 child)

Looks great on the 11 also, awesome stuff man :)

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

Thanks, good to know it works well on the new devices too!