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 7 years ago.
Improve this question
my app is an app for nightlife events. It's going to have two type of users:
user 1 is the normal user who looks at event
user 2 is the owner of a bar or a promoter.
These users don't have the same privilege, and can't do the same things. So the layout and functionalities won't be the same,
When the person logs in, I'm able to know which account he owns (thanks to my database). More precisely, user 1 has a keyAccess =0, user 2 has a keyAccess =1
I'm thinking of the code design of my app. What is the best way to handle this multi-account ?
I've thought of creating each time 2 types of activities, and check the value of the keyAccess before launching the intent. Is it good? do you have a better idea ?
Thanks a lot
Welcome to SO. A note - a good question shouldn't be opinion based, you need to ask a concrete question.
Plenty of bar app's exist and in my time working in the field I even saw some tutorials on just this. The simplest option is to create two separate apps or at least separate Activities, particularly as the only thing these two things share is the database (This applies whether you've set up as a web service or it's all on a single in-house device)
If you insist on a single app then just change the fragment or layout shown based on that boolean. There are really so many easy options available that it is impossible to give a more decisive answer to your question.
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 last year.
Improve this question
i want to contribute to a fandom i'm in and also practice my coding, so i wanted to make an app that would let the user keep track of the event stories they've read. but i don't know where to start with this.
i can add extra features like scoring and total stories read later on, but for now i need an idea of where to start. i think i've heard java would work for this? but would that even work on android and ios both??
once i know what programming language to use i need to find something to code this on, as well as how to even hold information in a database. (similar to myanimelist and how it has a database of entries that you can add to your own list.) likely with a login system--but one step at a time.
what are the basics i need to know to start? and where would i build this app? thank you!
If you want a single application that can work on both ios and android then go for Flutter or React Native. For your question regarding where to keep database and how login system works you will need to study at-least one of the systems in some depth.
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 5 years ago.
Improve this question
Ok so first off: I am a complete noob when it comes to Android app development. I used to have Android studio and wanted to make an app. I found it very confusing and hard to learn.
Second: I know HTML and CSS pretty well, but not JS or XML or any other languages.
I want to make an app that is basically a vault. When you open it, you get a login screen (with fingerprint login preferred). Then you login and are presented with a vault to store images, files, and etc.
I have no clue where to get started or what to learn. I want to learn how, but it seems very confusing to me.
I could also make this a web app so which ever is easier, let me know.
Thanks for the help!
What I suggest is you start with very small projects. In each one, aim to make something you haven't tried before (don't be repetitive in your apps). I suggest you make the following apps, so in each one you learn a little about what shall be useful:
+/- Calculator
Application which asks for a password, and if correct, sends you to a second activity
Application which can save information even if the application is closed
Application which can shows a series of images one below another
(scrolling down)
This will get you a nice idea on Android Basics which will be useful for your project. If you were to jump directly into it, you would find yourself in a sea of abstract information and have no idea what to do.
Remember: small projects give you better understanding. Google and StackOverflow are your best friends
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
Hello I am trying to implement an feature in one of my app so that it can be installed only on one device i guess trying with Device ID is one method Or are there any other methods to do so.......
If you are putting this on the Play store, users can always download any paid software again, as long as any device is linked with the same Google account used to purchase the app. This is designed to stop people losing apps should they get a new device etc and paying for it multiple times.
After reading your comments I believe what you wish the app to do potentially breaks Google Play TOC's. That said, you have not really described what you want to do well enough.
You could require the user to register with an email address before using the app. Maintain a database of emails that have been used to register the app and if an email has already been used, block them.
Note that while this is technically a solution to the question you asked, setting a limit like this is just going to irritate your users and is more likely to cause sales to go down (the few who buy will leave negative reviews, causing others to not buy), not up.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
The presenters in the Google I/O session about Android Beam made some comments about "breaking Beam by adding things to it." They used an example of Beam being added to the Share menu, which is bad because Beam should be "magical" and "simple."
The problem that I have is that with no UI, Beam has a big discoverability problem. The average user will never use it if they don't know it is possible.
What are the best practices to let the user know that she can tap to share?
I'm creating a chat app where users can add others by NFC (and other ways). There is an activity where the users can see how to connect to others. In there there is also a piece about NFC. I guess when my users know by then that this is possible they will use it. Still... not all the phones have NFC yet, so users have to ask others: "Oh, umh, you have NFC?" Which they probably won't do to people that they just met or if the user isn't a geek.
I guess the best way to let users know they can use NFC to share stuff is by implementing it in all apps out there so it becomes default that it is there. Untill then, you should just tell your user it's possible like I did, with some text, symbol or animation.
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 7 years ago.
Improve this question
I am looking to find the most efficient way to create an application that has a 30 day trial and then forces the user to buy the full paid version if they like the demo's features.
I was looking for suggestions as the best way to implement a license for the app. Here were some thoughts I had:
-Sharedprefs - This would work until the user uninstalled and reinstalled the app. The trial period would essentially start over.
-Use Device ID - I thought I could get a device serial number and upload the data to a server. Then I came accross http://android-developers.blogspot.com/2011/03/identifying-app-installations.html that showed the issues with trying to get a user id for a device.
UUID- It seemed like this was the best option. However, would someone be able to give me an overview of how to implement this and how it works. Also what are the limitations.
A sample implementation is already presented in the blog that you have cited.
Limitations: For your case, UUID won't work. Since, the user can actually delete whatever file/UUID you use for tracking (not easy, but doable)
Your requirement is to track devices. So, perhaps, go for telephony ID, Mac ID or a combination of both.