My app currently texts the user's GPS coordinates, after which the receipent enters them into the MAP app that comes with our iPhones. I just discovered that it is somehow possible to create an icon that the receipent merely clicks on to bring up the MAP app, where it displays a map showing the location of the coordinates, along with the exact address. I was so impressed with the accuracy and ease of use that I want to modify my app to text an icon, instead of the GPS coordinates. I spend all day researching but can't find how to do it. (Maybe I haven't looked in the right places, so please excuse me if I'm wasting time.)
The icon I'm trying to create (and text) is the one that you would create if you were looking at a location using the MAP app. After you tap the disclosure button it displays detailed info. At the bottom of the screen is a button entitled, "Share Location." If you click it, you then have the option of clicking another button entitled, "Message." a text message gets generated with an icon that represents a pin with a red head. This is what I'd like to create.
If it's possible, can somebody point me to where I can find more information, hopefully, including sample code?
Not all users have the ability to text images. The best option might be to just use the text... Also when you ask how to create the icon, what do you mean? The actual image?
Related
I have tried to do this but can not seem to get it to work. I noticed even the standard map in Apple doesn't let you do this. Is it even possible?
My experience with the map is, that is is not interactive. You can add a spot, but not react on user input. If the user taps on the map the built in watch kit map app will be opened.
I am bit confused to make screen over ios and getting challenge to do the task. I have a image that is either clicked by camera or taken from library. After getting it from library/camera user will show some tag over the picture. Let say i have a girl picture who wear a shoes , skirt, top and a necklace. When user wants to post this picture to server these tag/button will be bounded to image and this image send to server. When user come to feed on which that image is being displayed all the button user created is getting on the image. So after getting image from server how i will identify the place in picture where i have to show the button so that other user can tap over them and get the details of the product. This is how i need in the app. See the picture below.
This is exactly happening over POSE iphone app. Here is the link of that app try to make some outfit there and see what happening.
https://itunes.apple.com/in/app/pose/id402272154?mt=8
I need to implement this kind of functionality i have some ways in mind but better before working over them i thought take some genuine advise from the people.
you must have to send cordinates also to server and fetch them too for other users
How do you setup in your application to show little bubbles with text and block the rest of the screen from being used and only allow a small section / button to be pressed. I am wanting to create a walkthrough to show users how to use the application and where to find things within the application when it is opened for the first time.
I would like to dim the rest of the application except for the part I want them to click on. Is there a framework already with these features?
There's no frameworks that provide this functionality, as far as I know.
One way you could do this though is to have a set of overlay images which you overlay over the whole screen the first time the user goes to that screen. To determine if the user has already been to a screen, I suggest you look at NSUserDefaults. To create the overlay images, I'd make the image the full size of the screen (i.e. 460x320 if you are showing the status bar) and then have transparent sections where you want to "see through" to the element below. Add a gesture recogniser to the overlaid image view to detect a tap and then hide the image and set the flag in NSUserDefaults to make it not happen the next time the user goes to that screen.
If you don't get a better answer, you could look at MAAttachedWindow on the page at this link. It's written for Cocoa, not Cocoa Touch, so you would have to convert it. I am considering doing this myself. You might find it to be worth the trouble, but I haven't looked at every detail, yet, so I couldn't say for sure. There are only tow files that are involved (.m and .h).
I'm able to show current location on mapview. It shows round blue color circle. When I click on the circle, it shows "Current Location".
I want to show users current location as green pin. on click of pin, i want to show "My Location" annotation. How to do it.
Please suggest me how to do it.
Doing so is a bad idea. The blue dot and associated animation is a convention that is adhered to by all MapKit apps. Your user might be moving too. A pin is associated with a fixed location. Someone holding a phone is not a fixed point.
Please really think about the MapKit standards and Apple HIG they are there to help your users understand and enjoy your app.
When I've learned that I have to write some code to make the iphone keyboard go away. I was quite surprised. I was surprised even more when it become apperent that it is just the top of the iceberg.
What are the expected UI behaviors that aren't provided by system OOTB?
Is the list below complete?
The expected UI behaviors:
Focusing next text field when [done] is hit
Hiding the keyboard when background is hit
Using Touch Up Inside to fire a button action. (To give user opportunity to change his/her mind)
Supporting the screen rotation.
Some of that is silly, but some of it has uses as well.
Focusing next text field when [done] is hit
Which field is "next"? If you have a large form with fields both next to and above/below each other, next might not be so obvious. Even if they are in some linear layout, the iPhone would have to work to figure out which one is next. Do you want to wrap around at the end of the form, or dismiss the keyboard, or submit the form?
Hiding the keyboard when background is hit
I mostly agree with you here, though there are a few cases where this is useless. For example, adding a new phone number in the contact app.
Using Touch Up Inside to fire a button action
This one I really don't get. I can only guess that it's designed to allow you to use buttons instead of the touchesBegan/Moved/Ended methods. I guess it could be useful, but I've never used anything but Touch Up Inside.
Supporting the screen rotation
Many apps just don't work in any other orientation, such as games. If you want to use rotation, you only have to add two lines of code assuming you've done your layout well.
I hope this helps explain some of the strangeness. Aside from the keyboard dismissal, I've never really found anything too annoying. The one thing I wish they supported was using the highlight state of UIButtons for the set state. It would be a quick and easy toggle button, but I've taken to screenshotting a highlighted button and using that for the background image of a selected button.
Want a rounded rectangular button that isn't white? Since that one uses a background image, you can't just click something somewhere that makes it the color of your choice. You have to create your own image or you could even use CSS (WTF!?) to do it.
Unfortunately, the iPhone SDK lacks a lot of helpful things one would think would just be there. However, many people have taken the time to write wrappers for many of these kinds of things to help facilitate development - a quick google search into the functionality you are expecting may turn up a lot of useful answers!
For example, you could make the keyboard go away when you tap outside of it by creating a new view when it appears, and placing that view behind any user-interactable views on the screen. When that new view is tapped, it will become first responder and cause the keyboard to slide away (because the UITextField is no longer first responder).
Such a thing could be easily implemented as a drop-in fix for pretty much anything you'd need it for with very little code.
Still should have been included in the SDK in the first place, though!