Apps Building an Android application to a professional level?

[croninberg]

Hi guys,

My first on here. I'm a final year computer science student and my final year project involves building an application for Android phone, and Watch. I have little experience with Android, so want to find out what's the best way to go about this. I put professional into the title, because I want to make the app like it would be in the industry.

I've done a lot of research but finding it hard to get a solid foundation on what way I should be going about it. I would like to bring in Java Spring for the back-end as I see that's really popular, and have used it a little for web applications over the summer. People have recommended Firebase as my database, but would that really be used at industry level?

So if there's people on here who work as Android developers, could you give me some advice and tips, to how I can best make the application, as I hope to use what I learn to hopefully get a decent job next year when I'm finished.

Any help would be great,

Sean.

 

[Deleted User]

First read the sticky posts at the top of this forum. Your starting point is to download the Android development tools.

If you wish to develop for a smart watch, then you'll need to develop both an Android wear app, plus a partner Android mobile app.

Adding a back-end web application/server adds another dimension to your project. It's a lot of work you're taking on here. But take things one step at a time.
Btw how long do you have to complete this project?

In terms of database, then you could use MySQL, an industry standard open source database product. It's very widely used.

And if you want to develop to a professional level of quality, then also consider the following:-

- Design and modelling, using tools such as UML class diagrams
- Good code architecture. Definition of interfaces and packages
- Testing overhead. Development of unit tests to ensure high code quality
- Slick graphics (icons etc.)
- Workflow and UI design. App should be intuitive for the user.

Generally people are too quick to get straight to code. Usually it's best to try and get things clearly defined in a design phase. This also flushes out any misunderstandings and problems with the functionality of the system.
If you're doing this in a team, review your designs. Use a UI modelling tool (or failing that, pen and paper) to sketch out your screen designs, and app workflow.

 

[croninberg]

Thanks for the reply. Ya I have the Android Development Tools and been following some cool Udemy tutorials to get the hang of it. The deadline for the project is at least April/May. I'm thinking early May is probably the more likely date, so there is enough time I think to that bit of extra work. Well its a pretty large application I must build.

I was thinking MySQL for my DB, rather than using Firebase. I guess there will be a lot more work involved, but at least I should get a decent amount of experience. It would be nice you see to have a sort of full stack application built for this, to ensure a high mark.

I'm trying not to dive into the code, but my mentor has been putting a bit of pressure on me to hit targets every week, which is affecting the engineering side of things so is a pain. Like you just mentioned, I'd rather have a good grounding of a plan before I touch any code. Already I feel myself falling into a rut. So ya, I really need to hit the planning phase more starting from tomorrow.

 

[Deleted User]

Good stuff. Sounds like a great project. Best of luck!