Tag Info

Hot answers tagged

14

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


10

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


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


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


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 instead of browser view is useful in the following conditions: The mobile application of the website has additional functions that can't be done on the website alone, for example (stack-exchange) which you can use easily from the mobile application and you can jump to several sites on stack-exchange network in seconds ...


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

This is only a suggestion so don't scrutinize me. I did something similar to this. After a while you will notice that these scenarios are inevitable: The user opens the app loads a feed and then closes the app. A minute later the user opens the app and requests a feed that is identical to the one he just opened. This will increase server load and it will ...


1

The usable languages for developing Win8 & WP8 apps are JS, C#, Visual Basic or C++. The supported combinations are C# or C++/CX with XAML, C++ with DirectX, or JS with HTML/CSS Not sure about the books, but you can refer the below links to get started with developing WP8 apps. ...


1

For a really definitive answer, you will have to ask Apple, Microsoft and Google for what they consider to be code and why those restrictions are in place. Generally, "code" means instructions that can be executed on the device in question, either directly or through an interpreter. It thus also includes scripts. These restrictions probably exist to give ...


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



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