Is there a way to prevent iOS / iPhone from parsing a phone number like string in an email subject when sending an email to one of these devices?
Ex. Subject: "Test Email 1234567" results in an undesired phone number link
I've tried the solutions in the following questions, but those only work for links in the body, not the subject
How do you disable phone number linking in iPhone Mail app?
How do you dissable phone number detection in mobile safari
You could access the view and disable data detection, unfortunately you can't do that according to the documentation:
Important The mail composition interface itself is not customizable and must not be modified by your application. In addition, after presenting the interface, your application is not allowed to make further changes to the email content. The user may still edit the content using the interface, but programmatic changes are ignored. Thus, you must set the values of content fields before presenting the interface.
Related
For many years now I've included a link for users to view html emails in the browser just because it's an "industry standard". But it doesn't look great, and if it's the first thing the user sees it immediately gives them that "bulk email feeling" that makes them want to skip to the next message as fast as possible. It's also frequently shows up as preview text on gmail, apple mail, iOS mail, etc.
What modern email clients would display a standard HTML email so screwed up that it's not readable (assuming you're not using images for essential text, etc)?
Does anyone have stats of these "view in HTML" links being used at all in 2013?
It is best practice to include a "view on web" option in html email. Email is a game of percentages - it is hard to design for every client. If you go with the most consistent design - a static fix-width template, you still have the issue of many mobile users not being able to view the email properly. Anything more advanced like media queries are highly segmented also.
Some people just prefer to read on the web, while some older email clients don't display html at all, so it is a good fallback for them.
You could put the 'view on web' link at the bottom of the email if you prefer, but a better option is to include a preheader. A preheader is basically a secondary subject/title designed specifically to show up in clients that give a preview of the email content.
Being easily recognizable as a html/bulk email, I don't think is a problem - people expect that in today's world. The most important thing you'll need to counteract low engagement is supplying valued content to your subscribers and not sending too frequently.
I use an MFMailComposeViewController in an app to make it easy for the user to send me support requests. However, I get a lot of emails with the default message (+ the user's signature), but without any additional info added. I'm guessing this is because a kid is using the device and they're just mashing buttons. Is there any way to detect this case and have it not send the email?
Unfortunately, this is not possible.
From the apple docs:
Important: The mail composition interface itself is not customizable
and must not be modified by your application. In addition, after
presenting the interface, your application is not allowed to make
further changes to the email content. The user may still edit the
content using the interface, but programmatic changes are ignored.
Thus, you must set the values of content fields before presenting the
interface.
Is it possible to prevent editing when MFMessageComposeViewController shows up?
'Cause I want the body of SMS can't be changed by user and I think it's still legal.
Please help!
No the user has final say when using the MFMessageComposeView.
Your app is also prohibited from changing the content/recipient/body of the email when the
view slides up.
If you could do this it would be easy to paste in a different recipient, sniff the content provided by the user etc. etc. (especially in the Message App, you could swap the phone number and do terrible things.).
I guess this is the logic behind, you get to pre-populate the message, but the user decides from there on and until "Cancel" or "Send".
You should probably build a web service where you have control over the data
when it hits the server and make an interface for that on the phone.
I spend some days to search solution about this trouble :
I have an app wich receive notificaiton from other user. The single data, I have under server side is the number phone. So I want, when the notification is receive on the iphone, to link the number phone of sender to the addressbook of receiver for display, if the number phone is foud, the firstname of the sender to the notification.
This feature is like sms reception on the iphone, where is just the number phone used finally, and is linked to the address book.
The notification system on my app is enabled and run without trouble, but this feature is not resolved, and i found the response nowhere on the net.
Ok, i search more, and i think, this feature could be possible if the app can write under the Localize.string. In fact, it could be possible to write key value, like ("93019320"="Carla") and in the notification text the phone number "93019320" is replace by the string "Carla". But the second question is
Is it possible to write in Localiza.string under app?
I am new to iPhone development. I created an iPhone application, using which user can create a Business Card kind of UI in TableView. I want to know how can i send a Business Card(which i created programmatically) data into another iPhone via SMS? I want to know the technology which i should use to sending such thing from one iPhone to another via SMS or Email, i shouldn't use WiFi/Bonjour service which can send only upto nearest area.
thanks.
Calve/
SMS wasn't designed for this, and so it probably won't work like you're describing. Here's what I would do:
You have your BusinessCard object. Upload it to your servers and give it a unique identifier. This identifier is what should be sent to the other person, whereupon they can use the identifier to download the appropriate card.
If you wanted to be super cool about it, you could maybe construct a URL like: "card://12345678890", where 1234567890 is the identifier. You could then set your app up to respond to "card://" urls. Then send the card URL around via SMS. When a user taps on the link in their SMS app, it'll automatically open up your app (providing that they have it downloaded and installed, and that nothing else has registered "card://").
For additional awesomeness, you can allow people to create "shortcuts" to their identifier (like bit.ly), so they can send around "card://my-cool-business" instead of "card://1234567890".
You could encode your business card data as a base64-encoded custom URL, assuming it isn't too large. An example of doing this kind of URL-driven data exchange (which does not require uploading anything to a server) can be found here.
I doubt that you'll be able to encode enough information in the tiny size of an SMS message (unless you were just sending compressed text, no images), but this approach would work well with email.
Where MMS is available you can send a VCard formatted object attachment by that route. The receiving phone will detect the attachment format and allow you to manipulate it.
This will also work to non iPhone devices.