Thank you very much for the fast answer.
So its very simple actually without login.
OK, fine. But what is it you need help with?
The front end framework? The backend webservice? The database design? The MVC architecture? Coding? Signing and releasing? Building with Phonegap (locally or in the cloud?)?
There are so many aspects, so you might want to ask a bit more in detail. What is it that you can't do, yet? What aspects do you master?
@OP - keep in mind that we aren't going to write your code for you. This forum works best when you can point to a specific problem you are having. App architecture questions that aren't specific to PhoneGap are best handled elsewhere.
Also, given the nature of your questionnaire, you probably need to be very careful regarding security, privacy, and any medical laws regarding collection of this kind of information. These vary by location, so it'll be up to you to research this aspect. You'll definitely want to have a highly visible privacy statement indicating what you will and won't collect, and how the data is stored, and whether or not it will be shared with third parties.
I didn't ask nobody to write any code for me! Please read what i have wrote.
There are several addictians like internet additions, and no medical stuff will be asked.
Everyone should choose if he wants to send the data, and the professor is going to make it 100% legal, or do you think a professor doesn't know about it?
I mentioned that we weren't going to write any code because sometimes that's the expectation. I wanted to make it clear that this forum isn't the place for that. The way you phrased the question made me wonder if you were going to expect it. My apologies for misunderstanding. I did not intend to come across in an antagonistic manner.
- CSS: Forums Archive - CSS-Tricks
- Parse Server Github Issue: Issues · ParsePlatform/parse-server · GitHub
Then, when you're comfortable with these things on their own and then in the context of a browser, try to make it all work with PhoneGap. You'll run into specific problems which we'll be better equipped to help you with. Do note that there are no shortcuts here; mobile hybrid app development requres you have a pretty wide and deep pool of knowledge.
Finally, regarding privacy, security, etc., please, heed the advice and warnings from someone who's been there before you. I'm not saying that you shouldn't build the app -- I'm saying you need to be very careful.
Regardless of whether you think an addiction is medical or not, do understand that asking about addictions can be incredibly personal, which is why I wanted to point out that you need to be very careful here, especially when transmitting and storing that data remotely. Your users should be able to expect that you'll treat their data with the utmost care and security, and you can give them that assurance by providing them a privacy notice front and center.
Furthermore, it is not your professor's (or your employer's) job to make sure you do this in a safe or legal manner: it is your ethical responsibility to ensure that all appropriate steps to safeguard user data have been taken. If you aren't sure that you can do so safely and securely, then don't save or transmit the data. Once you're more comfortable dealing with remote security and you've educated yourself on the laws and such, then you can implement remote transmission and storage. (In a company, you'd have access to security engineers, lawyers, etc., who would be able to assist you with the various security precautions, legal regulations, etc.)
I mention the last because it's incredibly important to be aware that it is your responsibility to ensure the safety of your user's data. Sometimes we think our user's data trivial, but there are parts of the world where if even trivial data were leaked, the user's livelihood or even their life might be in serious danger. Perhaps that's not the case with your app and the target audience, but you can't know that for sure. Treat your user's data as if it is the most precious thing in the world. And if you then find that you aren't comfortable with that, then don't save or transmit your user's data at all.
I say all this to be helpful, not to be obstructive. I hope it can be taken as such. Along your journey you're going to come across individuals who have been where you are going, and have important lessons and warnings to impart. Learn from them, take their advice in that context, and you'll become that much better a developer for it.
All the best on your journey.
One more thing to toss in here. Parse is being shut down by Facebook, so that really is not long term solution. Firebase from Google might be a wiser choice.
Thank you very much for the time and your amazing answer.