Tap to exchange data between device A and device B [closed] - android

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 6 years ago.
Improve this question
We want to develop application which used to share important data in secure way. Idea is:
Data to be exchanged between phone A and phone B (and vice versa) when users “Tap” the phones together. The date, time and location of this action is to be recorded.
This should work anywhere (in buildings or in rural areas where there is no mobile signal coverage), and work cross platform (iOS, Android, Windows).
we want to know is it possible to develop such application ?
Thanks,

Yes, you can 'bump' phones and send over Bluetooth. You would use the accelerometer of the phones to detect the 'bump' part. The date, time and location you can pull straight from the devices (given you have GPS permission).
It would be a lot of work to develop right, especially across multiple platforms, and I believe an app like that already exists, for sharing contact information.
Also for future reference, you're probably getting down-votes because you're not asking specifically about code. Best of luck.

Related

What kind of knowledge and technologies needed to develop an specific mobile app? [closed]

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 3 years ago.
Improve this question
I had chosen to develop an mobile app for my final year project. The app is an parenting application that help parent to monitor and control screen time of their children and it have some function such as:
- Send notification to the parent mobile device when the child start to use the device.
- Lock the phone at certain time or by choice.
- Location tracking (optional)
- Report on use-time.
I'm familiar with basic Java and Android programming.
So what are the other knowledge (technology, mechanism, etc) that i will needed to develop this app.
It seems like you want to create parental control app and you can create it using "Android Management API"
Please refer Android Management API
Many companies installs this kind of apps in their employees company owned devices, many parents install this kind of apps in their child's mobiles to monitor their data usage, applications usage, their driving speeds etc.
Best of luck.

Create group over wifi [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
I'm trying to make an application that connects devices over the same WiFi. I'm fairly new to Android development, but I have basic Java knowledge. Now I want to know if my approach is correct?
My approach is as following: I first connect two devices together through WiFiP2P (this part of the code is finished). Next one device creates a SocketServer. That device will send his IP through WiFiP2P to the other device so the devices can now join.
Thanks in advance!
My understanding of WiFiP2P is fairly limited, but I'm assuming that it is trying to be what Bluetooth failed to be.
This approach sounds fine. There is even a page on the offical documentation about it.
My only thought is that you should add protection against malicious users performing spoofing attacks, if that is relevant to your app.

Android App on Multiple Devices [closed]

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 9 years ago.
Improve this question
I have been developing a concept for an Android application for doctors to use, and it involves the use of an Android mobile phone and a tablet in the operation theater. I will have a clickwheel sort of menu on the app running on the phone, and another instance of the app running on the tablet. When a user selects an option using the wheel, this event has to trigger the rendering of a view on the tablet. I'm quite new to Android development, so any help on how this could be implemented would be great!
Thanks in advance!
Krishna
You'll have to get the devices on the same network (of some sort). And device some sort of communications whereby the phone can send the selected choice over the network to the tablet, and the tablet can then react by updating its UI.
This communication could be achieved in many different ways: Bluetooth, or Wifi I think are the easiest two to implement. Which one fits your use case better would be something we wouldn't know without more information though.
In order for this to be accomplished you have to have some sort of messaging system between the devices. You'd likely make some server API call on menu selection on the phone. From there you can have the web service kick off a GCM message to the tablet OR have the tablet polling the server every x seconds checking for the change and responding appropriately.
As FoamyGuy stated, bluetooth might also be a viable option.

How to improve Android Beam discoverability [closed]

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.

Android: UUID and Licensing [closed]

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.

Categories

Resources