Cross-platform client for Systers & mentorship system written in Flutter

cross-platform client

cross-platform client for systers’ mentorship system, written in flutter.

how was it created?

i really liked systers‘ mentorship system, wanted to try flutter and had some free time during christmas.

rationale

mentorship system aims to be as inclusive as possible for everyone. it should apply
to user’s mobile operating system, too 🙂

work status

application is a high-fidelity copy of the android version. it has all essential
features implemented, though some may not work perfectly.

what works?
almost everything.

• login and registration
• home page
• profile page
• relation page
• members page
• changing password

what is missing? (in comparison to mentorship android)

• relationpage: updating availabletomentor and needsmentoring status doesn’t work
• about screen is basically about dialog. it’s very simple, more info should be added.

occasional ui bugs may occur – in this case, please create an issue.

overview

• app tries to follow clean architecure guidelines. logic is separated into 4 layers:
  • ui
  • bloc
  • repository
  • service
• app uses bloc pattern extensively
• to communicate with api, chopper is used
• to save jwt token, flutter secure storage is used
• if you find something in code that looks a bit odd, it might be some useful extension method from lib/extensions

web support

flutter for web is currently at technical preview stage. to test this functionality, i created
a separate branch.
i successfully ran this app in chrome.

web example here

it’s neither stable nor works smoothly (yet), but hey, it works.

unfortunately i was unable to make requests to the hosted dev server
because apparently it has cors disabled.
fortunately, it is at least possible to connect to the server running on localhost 🙂

to use web version of this app with your local server:

1. make these small changes to your local webserver
   to enable cors
2. run local devserver

future?

i’d love systers to accept this project as one of theirs. i do realize it requires
better documentation and has to be polished a bit, but i really believe these problems
are easy to solve.
my dream? i’ll be incredibly happy, for example, if students in next year’s google code-in will continue its development,
improve it and polish the codebase.