Tag Info

Hot answers tagged

9

You might want to have internal version numbers of your application to better manage your internal development processes. However, these numbers are of little use for the user. The usual purpose of version numbers is to tell the user if their application is up-to-date or not. When this is not within their control, it can at least be useful for support ...


5

There are two possible consumers of version numbers. Your internal processes and people using your service. With internal processes, version numbers help you identify when something was fixed and what has changed since them. By saying "we fixed this in version 1.2.3" you know where that was done and if you are now experiencing the same bug, you've got a ...


5

I think you are taking on unwarranted personal risk here. It's clear from your question you already realize a larger development team is necessary, that you cannot continue to do the work of multiple people without making untenable compromises to the quality of your work, the quality of your life or both. As a software engineer, it will be up to you to ...


3

I gonna go through your question paragraph by paragraph: For developers, What is the benefit of creating mobile app for a website? In which cases it is better than viewing it using browser? If your app needs to use stuff like SMS, addressbook access, or so then you have to use an app. But, many things can be done by now in HTML5 and JavaScript, just as ...


2

User facing code does not need version numbers. But if you are writing code that is consumed by external developers, then you absolutely should offer version numbers, and ALSO maintain multiple versions on your site. With a clear deprecation policy. Doing that will give you the freedom to make potentially backwards incompatible changes to your API, and ...


2

Using Mobile app from websites is useful when the mobile app has additional functions that can't be done on the website alone, for example (stackexchange) which you can use easly from the application and you can jump to several sites on stackexchange network in seconds without browsing. Also when some websites doesn't have mobile compatibility, which means ...


1

A combination of tools might help manage the complexity. I like to start with a stuctured yet descriptive approach (as distinct from a highly formalised approach) which is easy for humans to interact with. PM's should be comfortable with spreadsheets and it can be helpful to layout dependencies in tabular format. Eg a table for product x field ...


1

I would go back to the real purpose of version numbers: to uniquely identify a particular body of code. This is important in a lot of places, but there are several cases where I could see forgoing showing them to clients: They are used by clients who need to update (which you explicitly said you weren't dealing with). This also includes clients who would ...


1

There are a couple of ways to approach this, depending on your requirements and scale. First of all though, I don't believe a CDN is appropriate in this case. A CDN is used for caching of static documents to provide faster delivery of those assets to end users. It's not relevant for centralised storage or management of files. At the larger end of solutions ...



Only top voted, non community-wiki answers of a minimum length are eligible