olivierjm/chai-mobile-updates

realtime mobile updates

Hi, I'm Olivier JM

Thanks for checking out my profile, I am a passionate software engineer who enjoys getting things done. I maintain a few opensource repositories here on Github in my freetime and I do contribute to other opensource projects from time to time, I enjoy mentoring junior devs and those getting started in their software development carrier, feel free to reach out.

• In my past life I worked at:
  • Bongohive as a contractor for the e-Granary Digital Library project
  • Hackersguild as a software engineer, later to senior and Javascript bootcamp instructor
  • Sparkman Center at UAB as a lead engineer consultant - Remote
  • The ZIG as a senior software engineer
  • DoubleGDP as a senior Ruby on Rails/Reactjs software engineer
  • Rural Coding Series as a volunteer lead instructor in different technology camps to teach rural kids programming
• I used to write articles on medium and at olivierjm.dev
• LinkedIn Profile https://linkedin.com/in/olivierjm
• You can reach me at [email protected]
• My resume can be found here

chai-mobile-updates's Issues

native version

currently working on the native version of this repo, I had initially used expo but it doesn't seem to do most expected.

A readme would be nice

• Readme
  will solve the below and save time jumping in the project

Images on Mobile

For the reasons I know the images are not showing on IOS, this is caused by some issues with the network it needs https and it didn't accept ngrok.

@ikayz @alfeyo if you can manage to run it, you can test it out for me and see if it works on android.

domain

The server has been updated with an actual domain name and https certificate.
The websocket entry from the mobile app should be updated to the current so that the communication can happen.

react native

• react native run android. Not working.
  wow, nice to see the app and server in one place. Points on that

Ejecting

Due to some limitations I have been facing with expo, I maybe required to eject to native react-native, this will mean it will get more complex and probably more error.

The plan is to have it on separate on-going branch until it stabilised to be merged with the master.

Progress

I believe the best way of learning is by doing and this is why I don't mind sharing the code with anyone interested, this is an actual project and it is not necessary an easy one but I hope you can jump in, navigate here and there, find bugs and lint errors and fix them.

Ask where code doesn't make, I will try to help

Contributions are welcome especially on the app layout and user interface.

@alfeyo @ikayz