Tag Info

Hot answers tagged

13

I think that you can only lose by choosing not to communicate. If you don't plan to implement the feature now, at least suggest users that it is not in the current plan to implement, but might be considered in the future. This would not let users think that it's a feature they can expect soon and will send a message that you are not planning on it either. ...


9

Put together a stock "thank you for your interest" letter that covers the possibilities of a) features you will NEVER implement even if I show up on your doorstep with a bag of gold, b) features you don't PLAN to implement but maybe, and c) features you'd like to implement but can't right now. Send that. Because you ALMOST never know when you might find ...


8

A QR Code has a version range from 1 to 40. This information tells about how much data is stored within it. Version 40 has 177 rows and 177 columns (in some decimation called 'modules') for 31,329 pixels. It should be immediately clear at this point that this is the hypothetical maximum that doesn't take into account the error correcting or any of the ...


7

Ideally, you should use such requests as an opportunity to help you and users better understand the application. If you think of it, the very reasons why you prefer to ignore these requests are quite important information and you'd rather have them stored and documented than buried and forgotten deep down in your mind. If a request is ignored because you ...


5

Native applications use Objective C or Java. Web applications use HTML5, CSS3, and Javascript, running in a browser. Native applications may have to be written more than once, to satisfy the native platform's specific demands, such as programming language. Web applications may have limited access to the underlying native platform, and may not perform as ...


3

There are several different things protecting board games - not all of them may be in place. First, there's the copyright on the artwork of the game and the wording of the rules. Copyright is automatic - this is always protected. Next, there is the trade mark on the name of the game. These are registered and will typically be done for all professionally ...


3

The “P” part of a LAMP stack is a layer of CGI scripts. This layer can be provided by a number of languages. While PHP is the most common of these, other languages such as Perl or Python can be used as well. While a LAMP architecture is common and robust, it may not actually match your needs. For example it might make sense to not use CGI scripts and leave ...


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

Most Android devices can install application simply by opening an apk file in the browser. You can use self-signed certificates, so no problem there. It's more difficult with iOS applications. Everything you do there must go through Apple. Apple development site has lots of information about the different ways to do that but mostly it reduces to the ...


2

This question is way too broad to have a definitive answer. Business Analysts make whole careers from this. But to give you an extremely basic answer ... Listen to their ideas. Be humble. You've got to understand why they want this thing. What do they think it will do for them? What problem are they solving? It can be like many questions here: they are ...


2

There are many reasons why making an app has advantages. René said some. The ones I would like to add are : Native feel, touch UI optimizations and better UI frameworks. Existing web pages are not optimized to use on small, touch screens. Also, web technologies make it harder to optimize them for touch. So if you are going to invest into making the website ...


2

Those frameworks offer additional features, most relating to the hardware of the smartphones. Those include: accessing and manipulating hardware functions such as cameras, flashlight, screen brightness, gyroscope, vibration... software access, for example contacts, calendar, phone number, mails, HWID... running in the background, receiving (push) ...


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 ...


2

Any programmatic access to a web resource involves an API. As implementations differ, you may hear different terms: REST, SOAP, web service. If you're developing the website yourself, create an API. If the website is developed by a different team within your company, ask them to create an API. Discuss with them precisely your needs and draft together the ...


1

So I went and looked at 3GPP TS 24.008 and I found : For mobile stations supporting eMLPP basic calls may optionally have an associated priority level as defined in 3GPP TS 23.067 [88]. This information may also lead to specified qualities of service to be provided by the MM sublayer. That led me to ...


1

The metadata of a call will only be the bare minimum data required to make the call. So the capabilities of the origination point and the intended endpoint. Everything else would be added by the network and including any extra data should be stripped to avoid XSS attacks like this one on Who.Is.


1

If you want a canonical answer, I think you may need to go to the various standards that define the cell phone network, such as ITU-T, 3GPP, UMTS, etc. They're not light reading and some of them are fairly expensive to obtain. My understanding is that in classic GSM/3G/ISDN/UMTS/etc. call initiation, there is very little metadata beyond the dialed phone ...


1

If it's going to happen frequently on the application itself then you want to use native code. Yes, PhoneGap and Xamarin style products aim to allow you to write cross-platform mobile applications easily...but they are not 'lightweight' to add to an existing entirely native codebase. You can explore Xamarin - it would likely be a better fit than PhoneGap. ...


1

I think the other answers are on the right path in encouraging you to correspond with your users. one feature request turned into 7.. Based on this comment, you're not giving users enough feedback on the types of features you are open to. Maybe they want you to expand the capabilities/feature set but you're more concerned with performance and usability ...


1

The main difference seems to be that your code converts error responses into exceptions while your brother simply returns them. I believe that exceptions should be used to indicate programming bugs or emergency situations that threaten the integrity of a piece of the system. From this perspective, the library should probably not throw an exception because ...


1

Yours is better in the fact that you treat your corelib as an API. Throwing meaningful exceptions upwards to the application. His is better for being precautious by encoding the email and password entries. I really don´t see the need of the DepotServiceResult if not to avoid costly exception handling (which in this case should include a boolean property ...



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