mConference App - Capitalise on previous efforts

[Arnav Gupta]

Hi,

I am Arnav, a final year engineering student from New Delhi. I was a GSoC participant last year, and am willing to take part again.

I was interested in the mConference Framework project.

I have a suggestion here to make - there are already many existing efforts in this direction and it would be good to make use of some existing resources.
As part of my own GSoC project last year under FOSSASIA - we developed a project called 'Open Event' which was an event management platform for conferences
We built a Mobile app, a Webapp and a CMS for the organisers
The sources of various components are here - https://github.com/fossasia?utf8=%E2%9C%93&query=open-event

So basically there was already an API designed, a business logic defined, and a reusable App was made, that with changes to a config file ONLY could be recompiled for different different events.

It would be beneficial to take cue from that project, and re-use any components that we can. (Possibly using the server-side CMS which is very useful to let the organisers upload and update data about their events)

Best
Arnav

[Rahul Ahuja]

Hi Arav,

Thanks for your input. Our version of the application doesn't include a server component at all. The idea is to let the organizers of a conference create a fully branded application for themselves by just compiling the source code with a configuration file. This application would also work when the device is offline i.e. not connected to the internet. There is a possibility that the event organizer has two or three UI schemes to choose from - as to how the application would be defined in terms of UX.

The future possibilities of the project could very well be to find a place as a new template in out toolkit which creates other applications like this. 

> It would be beneficial to take cue from that project, 

> and re-use any components that we can. 

> (Possibly using the server-side CMS which is very useful to let the 

> organisers upload and update data about their events)

Sure, we are not reinventing the wheel here so reusing components is totally fine. The problem is we do not have a server side component for our app (nor a CMS).

[Arnav Gupta]

So in a way, you mean it will be similar in functionality to the Android Toolkit templates? THere will be two apps, one being the 'runtime' one that will have fixed code, and will depend on a particular 'configuration', and a 'builder' app that the orgainser will use to create the 'configuration' and package it inside the 'runtime' app and release it right ?

That's makes sense.

[Rahul Ahuja]

 

So in a way, you mean it will be similar in functionality to the Android Toolkit templates? THere will be two apps, one being the 'runtime' one that will have fixed code, and will depend on a particular 'configuration', and a 'builder' app that the orgainser will use to create the 'configuration' and package it inside the 'runtime' app and release it right ? 

Yes, that is correct. For the scope of this GSoC - we would be focussing on the development of the application and a simple web form to generate the configuration XML file. The integration of the app as a template in the BuildmLearn Toolkit wouldn't be in the scope for this summer.