Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
i and my friends make same projects in java. We decided that create own framework. But i don't know how to follow technical way? how to customize our structure to every project? how to design template engine for example? Should we be independed from other frameworks (spring,struts,ejb etc.) ? we want to develop this structor.i am confused.can you advise me?
From my experience, if you're not rich, first thing you need is to identify a niche and have a client to pay for the first development.
After that, you'll have to develop a solution with some nice code architecture that allows you, at the same time, to deliver something nice and that can be customized for other similar clients.
Sometimes, you can even try to deal with your first client to be a partner, providing feedback and helping you getting other clients for you (sometimes, it's a win-win deal and they can help you selling your software if they have the right contacts).
At the same time, you need to have a vision of what your product can do. This mostly depends on your niche characteristics. What backend they use most? What OS? Do they want integration with any other product? Other platforms (mobile for example)?
This is not the developer job, but it's more like a marketing task to be assigned to a product manager, so my tips here are basically
build something that solves a problem for someone that can pay
learn about your niche
try to establish partnerships
find a good / experienced product manager
Good luck
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
so here I got an open-source Android app which I must analyze and identify the structure of, things like its libraries, high-level architecture, configuration management, and testing facilities.
Now I understand where and how to look for the last two, but I still rather confused on how can I identify the libraries and architecture.
So what I'm asking is, how do I identify the architecture of an app and the libraries it uses? where do I look for it? what part of the source code? are there any tips to do this?
If there is any other info that I should provide, please do tell me.
Edit1: this is what I meant by high-level architecture, using Firefox as an example, but it doesn't have to be this technical, something more simple is also okay >>>
There are 1000s (maybe even millions) of questions on stack-overflow regarding Android development. The android documentation is itself highly exhaustive. And a simple query like "add library android project" can lead someone to answers like this.
What I am really trying to say is, a lot is already there. You just need to use it.
As for the original question :
Libraries
The dependencies can be found here. These are the external libraries that are used by this app.
-
Architecture
About that, you will mostly have to go through the code. Using Android-studio for that can be really helpful. You can use tools like this, but mostly, you will have to go through the code and understand it.
Furthermore, since its opensource project, there should be good documentation about it.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I am new to android studio and would like to make an app that is similar to Goodreads. Can someone outline the key components of making an app like this. It would also be great if I could get some kind of template that I can use. I imagine some of amount of the user information will be kept on the device while some of the other larger sets of information will be kept on a database. What would the code connecting these two parts look like and what other important parts have I missed. Thanks in advance.
Android is a big world and doesn't exist an easy way, I mean all need time to be good at something, but well is not impossible I recommend you start with the Udacity courses
Basic Level:
Developing Android Apps by Google
Android Basics: Data Storage
Android Basics: Multiscreen Apps
Android Basics: Networking
and latter star to flow important people on android world
Android expert even follow in twitter
after that, you have a basic knowledge you can start on other courses https://caster.io/ is a good choice for learn MVP MVVM and other things
also study general programming and Software Engineering : Desing Parrents, Clean Code , Clean Arquiecture, SOLID principles, Versions systems like a Git.
well that my advice for you, good luck and never stop to learn!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am currently in the process of analyzing the work of developing REST APIS for an Iphone Application using Java:
Firstly, Has anyone worked on development of REST APIs for iPad app or any other kind what is the kind of duration that requires to do it...and are there frequent changes in the REST APIs so that the project is a long one and my job is secure...or in general once you make APIS in 4-5 months maximum then that is THE END?
Are they something that a guy like me with no such experience in development of REST APIs can take up, are they in general something that only a guy with relevant experience can do?
If there are any good material on the internet about making them or anyway for me to get started with and go ahead with this:
I have just received the information that we need to develop 6-7 APIs for a start,,,any experienced guys about how much time it can take here is a sample workflow:
We have to click on Google maps..and based on longitude and lattitude we have to find a list of wholesale dealers related to our domain in that point and have to fetch them in JSON/XML Object...
Once the APIs are there, they are there and shouldn't change too often because it could break the app. So better put a lot of thought in the API design before you release it. How long it takes depends completely on the project. I can develop a REST API in a day, it could also take months, depending on the complexity.
It will take longer if you are inexperienced because you will need to do a lot of reading, especially when it comes to the architecture of the APIs. Again, impossible to say because we don't know your current skill-set. But in general: sure, if you are willing to learn you can do it, I don't see anything that would prevent you.
Lots of.. for a good framework have a look at Jersey. I also once found a good read about REST APIs in general: Link
As a conclusion, it's not necessarily only about developing the APIs, but also about the data you are trying to provide. Does that data already exist? Can you query it easily? How much logic do you still need in order to provide useful APIs? Those are the questions you should ask yourself as well.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
How can I create a site that users can manually make their own websites using my control panel in the site like Yola or Weebly that are free web developers. I think they use JSP but not sure. Can you help me that what kind of language they make those sites?
You could use any server-side language to develop a "site for making sites". PHP, Java (JSPs), Ruby/Rails, Python/Django... there are a lot of options. Some languages are better for certain tasks than others, but pretty much anything on the market would suffice for creating the website-making site.
As for "how to create" such a "site-building site":
You would need to supply users with templates, tools to edit those
templates, and ways to change the metadata about their sites.
You would also need to provide hosting for your users. You might come
in the form of subdomains, like jacksonssite.awesomewebsitemaker.com.
You would also need to make sure that your templates create pages
that are secure from "hackers" and the like.
You might also need to create tutorials / hire a support staff, to
help the technologically-illiterate use your tools.
And many more things as well.
It would be a complex task. If you are a beginner to web programming, undertaking a project like this would be far too ambitious.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm thinking about developing a web app to visualize the agile wall. The reason is that the project I'm working in has multiple distributed teams, so it is very difficult to share the information on the agile wall across the teams. I know some tools like JIRA do have agile wall functionality built in, what I want to have is a dedicated agile wall web app which could potentially integrate with those popular project management systems.
Does this idea sound sensible and interesting to you? Please let me know if you get better idea about sharing the agile wall across distributed teams.
Thanks.
John
Have you looked at Mingle from ThoughtWorks?
I haven't looked at it recently, but I'd expect it to be open to integration with other systems.
Even if you end up wanting to write your own, you should look at Mingle to see what a similar system looks like.
I'm not sure how well the card wall translates to a small screen. I've seen one similar implementation of something like this (www.cardmeeting.com) that I was not impressed with. One of the drawbacks to it is that the cards are unreadable until you click on them. That being the case, the tools used by most commercial vendors to capture stories at least the advantage that you can immediately see the titles on the stories even if they don't implement the wall format.
Another concern that I have is trying to take a passive information radiator and insert it into an active presentation medium. The wall format works partly (or even mainly, I haven't really looked at the research closely) because it's highly visible but not intrusive. Whenever you see it you get an immediate snapshot of the current state of the project. Translated into a web browser, you lose this aspect. It's not clear to me that in an active medium, where users need to navigate to information rather than simply absorb it, if the wall is still the right tool.
Take a look at Simple-Kanban. All done in a single HTML file.
Before you start implementing your own tool, take a look at:
http://www.userstories.com/products
I'm sure you can choose something appropriate :-)
Guess which one is ours...
Regards,
Marcin