I hope I am posting this in the right place.
I am looking for an Android developer to develop a database application to run on a tablet PC.
If you are interested please contact me
Thanking you
JP
What is that app about..
I am interested..
Thanks for the interest.
The app would be database driven where a user would login and select a certain publications to quote on. He would input the size, discount and about 5 other fields, including calendar dates. The app must then calculate what it would cost the client. The user must b able to save this quote so that they can later enter additional fields or info before mailing it to the client.
The app also has additional information that the user can access, such as readership demographics about the publication.
That's pretty much it. I have a web based app, but not all users would hav internet access when they are in front of the client, hence a stand alone app on the unit. The database on the unit would also need to b updated twice a year.
Let me know if this is possible and how long development would take. I know this is a very brief detail of the app, but if u could indicate some costs i would appreciate it.
Thanking u
JP
Is there no-one to develop an application?
Contact info
PokerRebel said:
Is there no-one to develop an application?
Click to expand...
Click to collapse
hi,
you can email me your contact info and project requirement on [email protected]
Hi samarpatel
I have sent you a mail with a brief outline of the project. Please get back to me at your earliest convenience.
No matter if the app is free or paid, as a developer you want to offer a good support to the end users. Why? Because as long as they are happy they will continue to use your app and they will recommend it to others. So it is in your best interest to do your best and resolve issues that customers are reporting, implement requested features and solve as many bugs as possible.
To that end, you must ensure you provide easy to access means of communication between you as a developer and the end users. There are many ways you can achieve that and I will list a few I am using and the more you can provide the better so we can put together a list:
Create an email address or use one you already have (I prefer the former) and provide links on Google Play and inside the app. It is nice if you add an accessible menu item that says (Suggestions/Bug report/Support/Etc) that will start an intent chooser for sending emails to this email address
Use forums (XDA ) and post your app and frequently visit and answer suggestions/questions. There are a lot of helpful users there that will test the app and discover bugs, suggest new features and it is very good if you can keep the thread hot so you keep the interest up. Users like feedback and makes them feel important (which they are) so try to answer as many posts as possible even though you don't have a solution to the problem yet
Get social! Social networking is very helpful these days both for spreading the word about your app but also for customer support. Create profiles for the app on all major social networks (Facebook, Google +, Twitter, etc) and try to get as many users as possible. Post as many updates as possible and keep the users informed about changes to the app, answer to their comments and implement suggestions
Prioritization - build yourself a TODO list with priorities: for each update try to solve major bugs first that are heavily reported or that are causing big problems. Always find some room for improvements and user suggestions. Then fix small bugs and try to improve UI.
Localization is an important part of today's apps. Try to support as many languages as possible making easy for the users to understand the app and to better communicate their findings
Use the publish console to check for crash reports. Many users use this feature and send crash reports along with the stack trace and it is very helpful to keep track of major crashes and identify the root cause
Please reply with more tips so we can create a big list for everyone
Email is the number 1 way people ( from my experience ) contact the developer to ask questions, recommendations, etc. What I did in addition to all the things in the op was create a cheap 5 page website with Godaddy website tonight its like $100 bucks a year or something. They also auto optimize your site for mobile viewing!Then made a contact us page, were users can choose a reason for contacting us. This works really well and you can set up an auto responder to send them a message letting them know you got the email.
I always try to answer emails immediately (during business hours) but always within 24 hours. Having a great customer service program even if your a solo dev like I am will translate into 5 star ratings based solely on customer service!
Have a lax customer service program and you will see the negative 1 or 2 star ratings pop up again based solely on customer service. It shouldn't take anyone more than say 48 hours to re connect with someone and at least start the process of answering their concern.
You can see the contact us page here
Good policy will turn into good reviews and good downloads!
:good:
I've put a feedback page in all my apps.
You don't even need to create a new email address. Just use your personal email address and create an alias. That way it looks formal on the outside but messages go to same inbox as your personal one, only have to check one inbox everyday.
HMMMMMM!
FIRST OF ALLL EMAIL AND AFTER THAT XDA POSTS.........:victory:
email or the message box is very important. But it's also important to reply to their questions promptly.
Free Customer Service SDK
Replying promptly to customers is essentially the first step towards good customer service. If you are an iOS app developer, looking to impress your customers with excellent customer support, try out Freshdesk's Mobihelp SDK ( [freshdesk.com/mobihelp) you can snap-in to your app and start communicating with your customers from right within your app. I'm sure it will be of great help in your customer service efforts!
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
kulisgames said:
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
Click to expand...
Click to collapse
In my experience, if the app is something people desperately need (e.g. utility) or want (e.g. game) but it isn't working quite as they expected, they will be vocal. Not hearing anything from users is usually a warning sign that nobody was too excited about the app in the first place, or that not that many people downloaded the app in the first place.
If I see a crash on Google Play I assume that the same crash occured for 10 others who didn't bother reporting it. So I try to fix it ASAP.
You could use Google Analytics to report crashes without user prompt.
Regardless of the above, it sounds like you have a general marketing challange which is much more critical than that crash report, so you should investigate marketing and promotions in general.
kulisgames said:
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
Click to expand...
Click to collapse
Bad reviews on google play
slackydroid said:
No matter if the app is free or paid, as a developer you want to offer a good support to the end users. Why? Because as long as they are happy they will continue to use your app and they will recommend it to others. So it is in your best interest to do your best and resolve issues that customers are reporting, implement requested features and solve as many bugs as possible.
To that end, you must ensure you provide easy to access means of communication between you as a developer and the end users. There are many ways you can achieve that and I will list a few I am using and the more you can provide the better so we can put together a list:
Create an email address or use one you already have (I prefer the former) and provide links on Google Play and inside the app. It is nice if you add an accessible menu item that says (Suggestions/Bug report/Support/Etc) that will start an intent chooser for sending emails to this email address
Use forums (XDA ) and post your app and frequently visit and answer suggestions/questions. There are a lot of helpful users there that will test the app and discover bugs, suggest new features and it is very good if you can keep the thread hot so you keep the interest up. Users like feedback and makes them feel important (which they are) so try to answer as many posts as possible even though you don't have a solution to the problem yet
Get social! Social networking is very helpful these days both for spreading the word about your app but also for customer support. Create profiles for the app on all major social networks (Facebook, Google +, Twitter, etc) and try to get as many users as possible. Post as many updates as possible and keep the users informed about changes to the app, answer to their comments and implement suggestions
Prioritization - build yourself a TODO list with priorities: for each update try to solve major bugs first that are heavily reported or that are causing big problems. Always find some room for improvements and user suggestions. Then fix small bugs and try to improve UI.
Localization is an important part of today's apps. Try to support as many languages as possible making easy for the users to understand the app and to better communicate their findings
Use the publish console to check for crash reports. Many users use this feature and send crash reports along with the stack trace and it is very helpful to keep track of major crashes and identify the root cause
Please reply with more tips so we can create a big list for everyone
Click to expand...
Click to collapse
Hi,
how can we deal with bad reviews on google play, reviews that comes from pepole that didn't understand the meaning of the app?
Thanks.
If you're looking for app support best practices, contact a big startup like Buffer or Squarespace and see how they respond to your question. Notice the friendly tone of voice, the detailed answers they try to give you, and the call for action at the end of every support ticket - whether it's to try and recreate the event that caused the bug or read a FAQ section. Do that a dozen times and you'll learn more about 'proper' support than any how-to article can teach you.
dimnikolov said:
If you're looking for app support best practices, contact a big startup like Buffer or Squarespace and see how they respond to your question. Notice the friendly tone of voice, the detailed answers they try to give you, and the call for action at the end of every support ticket - whether it's to try and recreate the event that caused the bug or read a FAQ section. Do that a dozen times and you'll learn more about 'proper' support than any how-to article can teach you.
Click to expand...
Click to collapse
Yep makes sense in my experience - personalise as much as possible and reflect the tone of voice of your app. Users will really appreciate it. Stay social.
Why not have some kind of in-app help?
Having a suggestions/feedback menu item seems to be the common thread here to provide good customer support.
But wondering - why not some kind of in app help itself? Sort of a Whatsapp inside the app? I feel email being a separate channel breaks the context - help within the app itself and in context would be so much easier for the end user.
Thoughts?
I know it is an old thread but there are SDKs that help you integrate a support chat right within the app. I have seen zomato use one of these.
Thank you for a list!
Hello!
CastChat is an app that allows you to send "broadcasts" to other users in your area, with a range of up to 20km. These broadcasts will be sent directly to your phone, so there is no need to refresh/pull from a database each time you want to see if there are any new messages. You can then message users privately, if you wish. There is no need to make any accounts!
I think this app would be great for anything that would require you to get help/spread your thoughts to other people that you may not know, but you would like to be in your community. Whether that looking for classmates to study with, or just talking about something that is specific to your area (sports, hanging out, etc).
I just released my app last night and am lacking users. I would greatly appreciate it if you could try it out and give me feedback on what you think of it (designs, colors, features?)
I will be checking back here frequently, so feel free to leave a comment!!
Just search for "CastChat" in the Google Play Store
Thank you!
Bump
Requirement
I'm assuming the other person would require the app too right?
patrickdass said:
I'm assuming the other person would require the app too right?
Click to expand...
Click to collapse
Hey, thanks for the question... you are correct. I don't think being able to send messages to everyone around you like that without their permission would be allowed.
I've gotten about 35 downloads, thank you everyone for trying!
Recently put out a new version which should help with some phones force closing the app on start!
Here is what I want to do. I would like to mod the Netflix app to also have a Facebook login just like the web version. It sounds simple but I am sure it is much harder than I think it is. I tried myself but my knowledge is not sufficient to do so. Any help would be appreciated. When you login the regular way you don't see any friends recommendations and well I think it is something Netflix should consider doing. Any ideas?
It depends what the mobile client uses for authentication, if it's the same as the website then you can try adding it by decompiling the app and creating your own version of it. However it would be a bit of a challenge.
Before you start anything, just send them an email about it as well asking for it to be a feature.
ticktockonthedot said:
It depends what the mobile client uses for authentication, if it's the same as the website then you can try adding it by decompiling the app and creating your own version of it. However it would be a bit of a challenge.
Before you start anything, just send them an email about it as well asking for it to be a feature.
Click to expand...
Click to collapse
I have decompiled the app but like I said Java is not my thing. If someone wants to take a look at it I will post it here. Looks like I got in way over my head on this one.
Watch the warez talk please. Thread cleaned of a couple posts concerning an app that hacks paid apps.
Thanks,
Darth
Forum Moderator
Hello developers,
I wait I have selected the correct forum, if it is wrong, please move to correct forum. I have trying to publish an app for Android auto. It is a simple chatbot. So, it is setting as notification on android auto. When I have tried to upload it as alpha version in order to try it on the car, google play team send me an email that said the following:
“At this time, we are only accepting apps within the Media or short form Messaging categories for Android Auto. Media apps that use TSS engine readout for content are not permitted at this time”
App doesn’t used TTS engine for read or listen, and it is chat bot, there aren’t music, sounds, etc. on app.
Could you help me in order to understand how Google classify it in order to fix? Because I have contacted with them but I haven’t received an answer in a week.
Thanks
I have got to know the reason. messages should be answered by humans and not bots.
Thanks
cansado2930 said:
I have got to know the reason. messages should be answered by humans and not bots.
Thanks
Click to expand...
Click to collapse
I'll close this up while it's no longer needed
Regards
Sawdoctor