Road map of features of the project

[iamareebjamal]

Lately, the focus of app has shifted from event information to social media and maintenance. Please first help the app align with features and information of API and also, the project has app generator which is left untouched. It has both front-end and a backend(in python) which needs to be evolved over time making it easier to generate customized apps while providing a better user experience and giving more information to the user. There are issues open regarding those technologies as well from 1 year back.

This should be the proposed roadmap for contributors:

• Focus on unresolved issues rather than new ones, preferably older ones. The ones which are really old show that they are somewhat peculiar in nature and thus require more attention, this will also help you establish that you are well aware of the project you are working on and have the capability to fine-tune yourself to an area of the project which does not fall into your comfort zone
• Also, take a look at App Generator technology and read the above point in this context. Same applies. Solve issues regarding it and propose new features to improve it as it the core technology of the project in conjunction with the app it is generating.
• Focus on the API information rather than what's visible in the app. Maintenance is a required part of the project, but adding new features (which align to the core functionality of the app) is something which makes the app move forward, We are at an incomplete stage and we need to functionally complete the application so that it provides every feature of the API. Note that adding or removing profile picture, truncating username is secondary to the App. We started with authentication and that is required nowhere else in the app, we are not using any part of API which requires authentication, so it is right now of least important. Think with the perspective of the user, when you download an application, do you want to sign up? What benefit will you get if you sign up? In an event portfolio app? And if you do sign up, and you find there is no difference if you didn't you'll surely think that there was no reason to do so. So think about either how to incorporate parts of API which require authentication and then provide them to users who are authenticated or only focus on the ones which don't even require authentication. Give priority to latter as you can do almost everything without authentication. This is not event management app where you need some authority. Our prime motive is to present user with as much information as possible without having them sign up (if it is not required)
• Understand the API, go to API docs and see if the models need updating, is there some field which is missing or the data type is changed, maybe some field was removed. Maybe some new model was added and we can use that to add a new feature to the app. Update the models(POJO), change their dependency. See if there are new endpoints, which functionality do they provide and how we can use it. Easiest thing to do for us would be to just go in model files of the project and see which fields are not getting used. This effectively means that we have that information and not showing it to the users. This can't be worse and not more easy to implement, just add some text view, imageview or a holder, a link perhaps and provide everything to the user. Everything else is of less importance than to show the user every absolute information about the event they have downloaded the app for. They don't want to change or crop or filter their profile picture, they have instagram for that.
• Go to the implemented frontend, see what features they have implemented, align with them and communicate how to make the user experience immersive. When you open your gmail application, you expect it to provide the same UI and flow as the web application. And web application is something which the person will rely on to get the information. The only reason one will download an application is if it needs to get notifications or some personalized information(None of which we are doing right now). Perhaps, offline capability. So, either inspire or get inspired by what has been built and do the same here, and see what features they have implemented which are not implemented in the app, create issues for them and work on them to make the user experience as seamless as possible. Or simply create features which are core to the app and can't be provided by the webapp so that the user is compelled to download the app. If features of the Medium app were less than that of its website, would you download it? Also, if you have done something they haven't, notify them and create issues so that they can implement it. I'm sure they have many contributors as well who are looking for real issues

Note: Some of this may sound like a rant, if so, please pardon me and please take it lightly, I have only said it jokingly. I have no intention to hurt anyone's feeling or target anyone

[mayank8318]

@iamareebjamal If I download an event app and i am attending the event then i would expect to get push notifications about upcoming events, trending news like posts or tweets etc which I dont think we are implementing right now. I think this can be a valuable addition?

[iamareebjamal]

Posts and tweets are a part of application right now. Push notifications aren't possible as of yet. And yes they are valuable additions

[mayank8318]

Since we are storing the data locally, can't we give notifications from our side and implement global notifications from the server when there is an api for it?

[jindalAnuj]

@iamareebjamal i have this api only https://eventyay.com/api/v1/events/6 is there are more api , if yes please help me

[iamareebjamal]

This is an event, API docs define what is available in the API. Also, this is old API. As lined in README, API docs are present here - https://github.com/fossasia/open-event-server

[mayank8318]

@iamareebjamal Currently the app does not have featured speakers display, which is displayed on the home page in the website. Was this omitted from the app for a reason? In one of the tests the property isFeatured is asserted to be false. Should we display featured speakers in the AboutFragment?

[dr0pdb]

Currently the app does not have featured speakers display

@mayank8318 It already has an issue and is being worked upon.