All,
To chip in to this discussion, I find it practically impossible to list all MFIs where a user can select his/her MFI before logging in to the App. One of the best ways I think we could probably have is every hosting partner to adjust the code and have their own app then a user shall be required to first activate the app using his email address / phone number of which the app should check onto which tenant the email address / phone number exist and automatically points the user on to that particular tenant. When a user changes phone then they must activate the app again in the new phone and the old phone should stop to function. The challenge would be if a user exist in more than 1 MFI hosted by the same partner and that person has used same email address / phone number in both. How will the activation be done? Alternatively, we could have the default app have a connection string where a user can change the URL. This might be technical and some clients of MFI would not know how to do it and thus shall render the app as useless. A serious thought should be put in to this before releasing the app. Regards; ******* Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: <mailto:[email protected]> [email protected] -----Original Message----- From: Myrle Krantz [mailto:[email protected]] Sent: 28 November 2017 02:08 PM To: [email protected] Cc: Denila Philip <[email protected]>; Mifos software development <[email protected]>; Naman Dwivedi <[email protected]> Subject: Re: DISCUSS: Personalization of Mobile Banking App by Financial Institution All, Allow me to bring this branding requirements discussion back to the list so we can broaden our information sources: How do banks want brand their app? I see two proposed solutions in Ed’s mail. 1.) By adjusting the source code and distributing a bank-specific app. 2.) By distributing the same app for all banks, then selecting the bank *in* the app. Does anyone see any other possible solutions? Do any of the domain experts on the list have a preference for one of these solutions? What do banks and MFIs want here? Best Regards, Myrle P.S. I wasn’t on the check-in call Ed is referring to here, and you don’t have to be to participate in this discussion either. *All* participants are welcome. On Fri 24. Nov 2017 at 11:46 Ed Cable < <mailto:[email protected]> [email protected]> wrote: > Hi all, > > Based on discussions during our last few check-ins, we wanted to > propose an approach to allowing end users to access the > tenant/instance for the financial institution they belong to while > still being able to download the app from Google Play store and > freeing up each partner from having to package up and build their own > app. Rajan will create a ticket on Apache Fineract JIRA to document > the needed changes but a summary of the approach we're proposing: > > For near-term to allow organizations to test the mobile banking app > and run against their own tenant, we’ll enable a setting to change the > baseurl which will only be visible in debug mode. So a partner could > download the APK we release, modify the baseurl in settings and share > this new APK with the organizations they support to offer to their clients. > > The long-term solution we’re implementing will be to build into the > initial welcome screens when a user first downloads the mobile banking > app, the ability to select from a drop down the financial institution > that they’re a member of, selecting this will then set their endpoint > and base url and then the app will be able to verify that they have an > account at the financial institution as has been implemented, create > credentials and then authenticate. > > For this to work, it will require partners or organizations that want > to be discoverable to share their baseURL as well as tenants at that baseURL. > This database of baseURLs and tenants will be maintained by Mifos and > will populate the drop down list that users select upon initial > download of the app. > > Enhancements to Fineract will have to include: > > > - > > Endpoint on our demo instance of Apache Fineract to fetch all base URLs > - > > Endpoint to fetch tenants from baseURL to make this work for > multitenancy hosting setups. > > > Ed > > On Fri, Oct 20, 2017 at 1:31 AM, Ed Cable < <mailto:[email protected]> > [email protected]> wrote: > > > Naman brought up a very good point in the comments on the GitHub issue: > > > > *@edcable < <https://github.com/edcable> https://github.com/edcable> I > > maybe missing something > > here > but > > financial institutions will have to anyway build and create their > > own version of app since they will be having a separate fineract > > instance and thus a different base API url that will have to be > > changed in the code.* > > > > *However, I do agree that an admin section in the webapp for > > managing these self service channels will be great.* > > > > > > While this might then make it the case that each organization needs > > to create their own version of the app, is there a means of having > > the the client download the generic app, then when registering based > > on which organization they specify they belong to, it identifies the > > tenant and > sets > > the base URL. Or since there is no separate authentication service > > that stands alone from Fineract tenant, that we can't do any of this > > registration/authentication without first having the Base API URL > specified. > > > > > > Ed > > > > > > > > On Fri, Sep 29, 2017 at 12:48 PM, Zayyyad A. Said < > > <mailto:[email protected]> > > [email protected]> wrote: > > > >> +1 for MFIs to be upload own logo in Web App which automatically > replaces > >> Mifos Logo when you connect to the instance. > >> > >> Have a powered by Mifos Initiative link somewhere. > >> > >> Regards; > >> > >> > >> ******* > >> Zayyad A. Said | Chairman & C.E.O > >> > >> Cell No.: +254 716 615274 | Skype: zsaid2011 > >> Email: <mailto:[email protected]> > >> [email protected] > >> > >> > >> > >> -----Original Message----- > >> From: Ed Cable [ <mailto:[email protected]> mailto:[email protected]] > >> Sent: 29 September 2017 09:29 PM > >> To: Mifos software development > >> < <mailto:[email protected]> > >> [email protected]>; > >> Dev < <mailto:[email protected]> [email protected]> > >> Subject: DISCUSS: Personalization of Mobile Banking App by > >> Financial Institution > >> > >> As we prepare to launch the Mifos Mobile Banking App powered by > >> Apache Fineract, one thing I realize we need to make easy for the > >> sys admin of > the > >> app is the ability to change the logo to that of the financial > institution > >> offering the app to their customers. > >> > >> Most organizations will want to have the app have the look and feel > >> of their organization (at least their logo) > >> > >> While some orgs will want to take the codebase and build their own > >> APK and distribute their own version of the app directly or through > >> the Play store, I foresee the real-life scenario would be the > >> financial > institution > >> would direct their end users to go to the Google Play store and > >> search > for > >> Mifos Mobile. The user would download that app and then when > >> logging in they would see the logo of the financial institution > >> that they belong > to. > >> This logo would replace where the Mifos logo is currently (we still > would > >> like to retain some of the Mifos branding in the app though). > >> Ultimately they might also want to change the mobile app icon too to their > >> org. > >> > >> Should we just create a section in the Mifos X web app, where they > >> can upload the logo they want displayed in the mobile banking app? > >> > >> Perhaps within the Mifos X Web App admin section there will be a > >> control panel of sorts where the financial institution can manage > >> their self-service channels (mobile and online banking apps). This > >> is where we can also put the user creation/management > >> functionality. It could also > be > >> where they could initiate in-app notifications from. As we improve > >> our customer support mechanisms through the app, incoming requests > >> could > come > >> here. > >> > >> I created ticket at > <https://github.com/openMF/self-service-app/issues/431> > https://github.com/openMF/self-service-app/issues/431 > >> to track discussion. Will likely need to create the appropriate > >> tickets on Apache Fineract and Mifos X web app issue trackers to > >> support the > same. > >> > >> Ed > >> > >> > > > > > > -- > > *Ed Cable* > > President/CEO, Mifos Initiative > > <mailto:[email protected]> [email protected] | Skype: edcable | Mobile: > > +1.484.477.8649 > > <(484)%20477-8649> > > > > *Collectively Creating a World of 3 Billion Maries | > > *http://mifos.org < <http://facebook.com/mifos> http://facebook.com/mifos> > > < <http://www.twitter.com/mifos> http://www.twitter.com/mifos> > > > > > > > -- > *Ed Cable* > President/CEO, Mifos Initiative > <mailto:[email protected]> [email protected] | Skype: edcable | Mobile: > +1.484.477.8649 > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > < <http://facebook.com/mifos> http://facebook.com/mifos> < > <http://www.twitter.com/mifos> http://www.twitter.com/mifos> >
