Of these four technologies, there are five broad categories of mobile payment systems:

• Mobile at the point of sale
• Mobile as the point of sale
• Mobile payment platform
• Direct mobile billing
• Closed loop mobile payments

Here is a closer examination of what each of these five categories are and their pros and cons.

Mobile At The Point Of Sale

Source: Mobile Marketing Magazine

Also known as the “mobile wallet�? this system allows customers to pay for things at a store with a mobile device using NFC technology, or the “Tap and Go�?method, via WAP. Examples include Google Wallet, Isis, MasterCard, Visa, and Apple Pay.

• Pros:
  • Most smartphones are now NFC-equipped
  • Quick, easy, contactless payment method
  • More secure than just swiping a credit card through a reader
• Cons:
  • Privacy concerns: because these mobile wallets often store credit card information in their systems, there has been questions of exactly how easy (or difficult) it is to hack the security. Additionally, there are questions of whether or not the company of the mobile wallet system are able to read the credit card information.
  • Mobile wallets are also slow to gain traction because 1) there are so many different kinds of systems, 2) there is no universal reader yet that will be able to read every app, and 3) they rely on cooperation between credit card companies, banks, mobile manufacturers, and mobile networks. Apple Pay has encountered some resistance by merchants looking to align themselves with CurrentC as their primary mobile payment option.

Mobile As The Point Of Sale

Source: Square

In this instance, the smartphone is used as a cash register, and does not require the consumer to be responsible for having a mobile payment system. The merchant uses a mobile device to process credit card payments. Popular examples include Square and VeriFone.

• Pros:
  • As a cheap and easy alternative to the cash register, these mobile payment systems are credit card-based, thereby avoiding the mobile wallet war.
  • It is convenient for small businesses that can’t afford cash registers and credit card processors.
  • Square, the most popular example, bundles all credit card feeds (bank, the card company, and the processor) into one single fee. This way, merchants don’t have to worry about paying three separate fees to three separate companies.
• Cons:
  • Processing fees might not be more competitive to traditional processors. Square takes a 2.75% off all transactions (and in some cases 3.50%), which is higher than most credit card companies.
  • It is not ideal for all businesses, especially those that are larger and bring in larger revenue.
  • Businesses that have abnormal processing behaviors or revenues that come in waves may trigger a red flag with Square’s fraud detection system, which could delay payments from reaching the merchant’s bank account.
  • Additionally, since it is still credit card-based, this does not provide a solution to the problem of credit card and identity theft.

Mobile Payment Platform

Source: Silicon Angle

This is a catch-all category for mobile payment systems that do not resemble the mobile wallet or using the smartphone as a cash register. Merchants can use WAP technology on mobile devices or consumers can send money to each over via a peer-to-peer WAP system. This catch-all category usually uses WAP payments to either charge the phone bill, the credit card, or through an online wallet. Examples include PayPal, Dwolla, and Serve.

• Pros:
  • Credit card and/or bank information is usually security-encoded and doesn’t require consumers to physically have the credit card on hand.
  • It is an increasingly popular alternative to SMS payments.
• Cons:
  • Like all mobile payment systems, it can be a target of possible cyber warfare.
  • Credit card or bank fees still apply

Direct Mobile Billing

Source: Angry Birds

Colloquially known as “put it on my phone bill�? charges are placed on the cell phone bill via in-app billing or through text messages via SMS. Examples include ringtones or games like Angry Birds.

• Pros:
  • SMS is a technology available in older cell phone models, so consumers do not need a smartphone to be able to purchase products
  • It is quick and easy to use.
  • There are no passwords, usernames, or log in needed like the other mobile payment systems. Credit card numbers and bank information are also not needed, which helps to alleviate security concerns as personal information is never transferred or given to a third-party.
  • Billing is handled entirely by the mobile service provider, so consumers don’t need to worry about additional bills to watch for every month.
• Cons:
  • “Put it on my phone bill�?is mostly used for purchasing digital content. It is very uncommon to see in-app billing or SMS payments used in traditional brick-and-mortar stores for non-digital products.
  • SMS often incurs a high and costly fee, and has been known to be slow in speed and unreliable.

Closed Loop Mobile Payments

Starbucks’ Christmas Bokeh by Piero Fissore

Okay, so this really isn’t anything like the traditional mobile wallet. Instead, closed loop mobile payments are more like a mobile version of the store credit card. The store company itself builds their own digital wallet and mobile payment platform system. A very successful example of this is Starbucks. Like a debit-card, consumers load up the app with money and use it toward their future purchases. These digital store credit cards can also save store coupons, track gift cards, and handle loyalty-rewards programs, thereby potentially saving the consumer lots of space in their physical wallet.

• Pros:
  • You save a lot of space in your wallet, which is especially attractive for people who can’t keep track of weekly store coupons.
  • It has the convenience of being a mobile payment system
  • All personal credit card or bank information that is used to load the store credit card can be done in the safety of your own home. This sensitive information is not transferred to the merchant at the point of purchase.
• Cons:
  • Although Starbucks has seen great success with their store credit card, it is a success that isn’t guaranteed to be replicable in other business models.
  • Adding money to the card requires an “extra step�?that could be too much of a hassle for some consumers.
  • Because it is “just another app�? store credit cards face competition from other mobile payment types.

Customized eCommerce Solutions

Logic Solutions can help you with your eCommerce and mCommerce strategy, development, implementation, and support. Find out how you can have a beautiful, functional frontend and a powerful backend to support your business needs.

Let us help you

Jennifer Pan is a marketing coordinator at Logic Solutions. If you want to get her attention, try talking to her about d20s, (board) games, sci-fi and geeky references, or cute animal videos…or all of them at once. Just don’t bring up her uncanny ability to roll natural 1s.

The post Comparison of Mobile Payment Types appeared first on 雷技信息科技（上海）有限公司.

Source: Silicon Angle

Forget cash and credit cards. Mobile payments are here to help keep your wallets slim and (hopefully) secure.

Consumers, particularly those in parts of Europe and Asia, have made purchases with cellphones for the past decade. However, these mobile payments are only starting to go  mainstream, and are set to redefine the way traditional and online business is conducted all over the world.

But first, what is a mobile payment system? This phrase can apply to a number of different technologies but the basis is still the same: it is a system for initiating and accepting transactions using a mobile device. This applies to how consumers pay for goods as well as how merchants process transactions.

Of course, one of the primary concerns with mobile payments is security. Recent security hacks and the increase in instances of identify theft have made consumers more cautious about their personal information. Large tech companies like Apple have emphasized over and over the security features of their products and measures taken to keep users�?privacy from leaking out into the world. And every product that manages to make a headline touts itself to be the ultimate solution to all of our cash-and-credit-card-heavy wallet woes.

There are generally four different technologies upon which mobile payments build their platforms. These are important to know when examining functionality and security.

• Near Field Communication (NFC): Contactless, almost instantaneous transfer of data between devices. NFC is often used in “Tap and Go�?payment methods, such as tapping the smartphone to a device reader.
• Wireless Application Protocol (WAP): With WAP, the smartphone connects to the internet, then pays via an online payment system (such as Paypal or Google Wallet) or by entering credit card info through the merchant’s website. Alternatively, WAP can also defer the charge to the phone pill.
• Short Messaging Service (SMS) Payments: Considered a bit more “old-school�? SMS allows users to pay for goods and services via a text message sent from the phone. The cost of the item is then added to the user’s monthly phone bill.
• In-App Billing or Direct Mobile Billing: Most commonly used when purchasing an app from an online store or a game, this system charges the cost of the product to the monthly phone bill.

The world of mobile payment systems is not limited to just these four technologies, though.  Small pockets of communities across the world are experimenting with new ways to transfer money from consumers to merchants. Here are some other examples to look for over the next couple of years:

• QR Code Payments: CurrentC is one company in the U.S. experimenting with using QR codes to purchase items. Although QR codes are not as common in the U.S. it is much more popular in Europe and Asia. It will be interesting to see if QR codes will catch on with American audiences.
• Direct Carrier/Bank Cooperation: No credit card number or bank account information is needed. Instead, the mobile phone and phone carrier become the front-end interface for consumers to purchase goods and transfer money via a mobile phone number. This payment system is in its very early experimental stages.
• Audio Signal-Based Payment: This sounds like something from a sci-fi movie. This payment system uses acoustic feature of phones to support mobile payments and other applications that are not chip-based. The microphone on cell phones can pick up these audio signatures to enable electronic transactions. The advantage to this is that all phones are capable of picking up audio signals, whereas not every phone is NFC-equipped.
• Bitcoin: Bitcoin is an online payment system that was developed in 2009 that utilizes virtual, alternative currency with no transaction fees, with gives it a leg up from traditional credit cards. There are also no middle men (like banks) to take additional transaction fees. Consumers can purchase their merchandise anonymously. Bitcoin has yet to gain a lot of traction in with the mainstream audience, though small percentage of merchants accept it. Some people are purchasing bitcoins as an investment, hoping they will  dramatically increase in value over time.

Customized eCommerce Solutions

Logic Solutions can help you with your eCommerce and mCommerce strategy, development, implementation, and support. Find out how you can have a beautiful, functional frontend and a powerful backend to support your business needs.

Let us help you

Jennifer Pan is a marketing coordinator at Logic Solutions. If you want to get her attention, try talking to her about d20s, (board) games, sci-fi and geeky references, or cute animal videos…or all of them at once. Just don’t bring up her uncanny ability to roll natural 1s.

The post What the heck are mobile payment systems? appeared first on 雷技信息科技（上海）有限公司.

Bring your own device (BYOD) is a policy where employees are permitted to use personally-owned mobile devices (laptops, tablets, smart phones, etc) to access privileged company information and applications.  BYOD is an increasingly popular business trend with both pros and cons that companies must consider carefully before adopting a formal policy.

A supporting argument for BYOD is increase employee productivity. Surveys have shown that employees are more productive when using personal devices, are more invested in properly maintaining the device on a more frequent basis, and require less training for a device that they are already familiar with.

Additionally, employees are also more likely to take their work home, which allows for work flexibility, and in turn boosts employee morale and convenience, demonstrating a flexible and attractive work environment.

Furthermore, asking employees to provide their own tablet and/or mobile phone saves the company significant costs by eliminating not only hardware but also software, maintenance, and possibly technology upgrade expenses.

However, some companies may be cautious in adopting a BYOD policy despite the significant cuts to tech costs and device management.  Common concerns about BYOD center around security and sensitive company information.  What would happen if there was a data breach?  What if an employee’s smartphone, that had access to the company network, was lost and untrusted parties could retrieve unsecured data on the phone?  Can or should businesses wipe personal devices after employees leave the company?

Employers that allow their employees to use personal mobile devices for work purposes should consider writing a clear, comprehensive BYOD policy that formally addresses such security, privacy, and control concerns.  The following is a non-exhaustive list of some questions a BYOD policy should cover:

• What devices are allowed or included in the policy?

• What level of access will be granted to the employees?  Will different employees have different access levels?

• What kinds of antivirus and protective software are required?

• If the employee owns the device, who owns the apps and data?

• What type of security should a company require and how will these requirements be enforced? Will remote access be available?

• Who is responsible for supporting devices?  What level of support will the company provide?  What costs or expenses for employee owned devices are the employer willing to cover?

• Will there be a virtual partition in the device to separate work data from personal data?

• What do you do if you find illegal information or activities on the device?  Does it make a difference if it is in an “area�?of the device that is not work related?

• Under what circumstances will the employer wipe company data from personal devices?

If you’re looking for some examples of BYOD policies, here are links to resources that you can get ideas from:

• Toolkit to Support Federal Agencies Implementing Bring Your Own Device Programs

• BYOD Policy Template

• Sample Policies for Schools

• 7 Tips for Establishing a Successful BYOD Policy

FREE DOWNLOAD: A Guide to Mobile App Development Platforms

Compare the pros and possible limitations of top six mobile development tools on the market.

Download Now

Jennifer Pan is a marketing coordinator and The New Recruit at Logic Solutions. If you want to get her attention, try talking to her about d20s, (board) games, sci-fi and geeky references, or cute animal videos…or all of them at once. Just don’t bring up her uncanny ability to roll natural 1s.

The post What is BYOD? Tips On Writing A BYOD Policy appeared first on 雷技信息科技（上海）有限公司.

Image Credit: Conversion Pipline

1. What types of apps have they developed?

We assume you will do the due diligence to find out whether prospective developers HAVE built apps, but you should also consider what types of apps they’ve created. Were they games? Consumer tools? Productivity boosters? Business or Enterprise apps?

Understanding the ins and outs of a high-performance video game does not necessarily translate into the ability to smoothly deliver, say, a sales force automation tool with secure data requirements. Developers should and can be versatile, but like any other field there are definite specializations.

2. What types of industries do they serve?

We won’t completely pass up a developer who hasn’t worked in our field, but it is certainly a bonus when one is familiar with the particulars of your industry. For example, if your app needs to be HIPAA-compliant, or adhere to stringent financial regulations, it’s much easier to work with developers who have previously satisfied those requirements.

3. What platforms do they know?

Delivering an app across multiple device types is certainly getting easier with the proliferation of cross-platform development, but it’s still important to ask a developer about their expertise. You might find you have a whiz at iOS programming, but a beginner at Android.

4. Do they perform the design work?

Graphic design and UI/UX (user interface and user experience) are CRITICAL for mobile apps. Users will permanently abandon a downloaded app in seconds if it provides a poor user experience. Development firms may offer design and usability services in-house, or work with outside firms. Some developers require you to deliver finished designs before the programming can start. Either methodology can be successful, and you should choose what makes sense for your project, corporate branding standards, or personal sanity.

5. Do they understand how to work with your users and data?

Many times apps involve grabbing data from an outside source, obtaining data from users, or both. You many need to use APIs, web services, and interact with the device itself to pull everything together seamlessly. If that’s the case, having a developer with expertise in data integration can save you a lot of headaches when trying to get information to and from sources.

6. Can they help you with deployment?

Maybe you want your app on public markets like the App Store and Google Play. Submitting your apps for sale involves an application process with code uploads, app review, possible contractual obligations, and more. If you don’t know how to do this yourself, you’ll want to make sure your developer can assist you.

If you’re creating an app for internal use by your employees, there are private distribution concerns to address. Do you need to control your devices with a Mobile Device Management tool? Do you have a BYOD policy, and what does it entail?

7. Are they asking the right things?

Good developers ask tons of questions. They want to know your goals for the app (brand recognition, customer loyalty, revenue generation, mCommerce, process improvement, all of the above, etc.), what devices you’re targeting, who will use the app, how you’re monetizing the app, what other apps do you like, if your tool needs an internet connection, where your current data exists, what security concerns you have, and so much more. They’re considering functionality, best practices, and optimal usability, while looking to avoid technical traps and App Store rejections.

FREE DOWNLOAD: Mobile App Development Checklist

Now that you know what to look for when hiring mobile developers, here is a handy checklist to help facilitate conversations with your developer!

Download this checklist now

Angela Kujava is the Director of Innovation and Chief Smoothie Officer at Logic Solutions. She is an ardent supporter the Oxford comma, and will challenge you to a duel if you believe the contrary. Should you find yourself about to duel Angela, it is valuable to know that her kryptonite is Doritos. She cannot avoid their salty, orange siren song.

The post 7 Things CEOs Should Consider When Hiring A Mobile Developer appeared first on 雷技信息科技（上海）有限公司.

Details behind the reason of this increased security measure are vague.

Phones made by Apple and Samsung (that means the iPhone and the Galaxy, two of the most popular phones on the planet) will be singled out, according to Reuters.

France, Germany and the United Kingdom have all agreed to participate in this security measure as of July 6.

Now for some positive news: Air New Zealand is now allowing mobile devices to remain on during the entirety of most flights.

Does your awesome business want an awesome app?

Logic Solutions can create one just for you!
From the coding to the design to assistance with the distribution to enhancements and maintenance, the awesome people at Logic will help you with your mobile game plan.

---

Create your mobile app today!

Pierce Courchaine is a marketing coordinator at Logic Solutions. When he’s not in the office, he’s rumbling around the country in a 1996 Honda Civic he lovingly named Martha. Martha’s air conditioning doesn’t work anymore, her power locks failed, her back left window doesn’t open and her 106 horsepower has made for some heart-pounding races against Vespas. For some reason, he’s the only one who can see what’s special about her.

The post TSA Wants You to Power Up Your Mobile Device appeared first on 雷技信息科技（上海）有限公司.

Many company leaders are posed with the difficult question of, “Should I develop my project in-house or with an independent developer?�?Obviously, we want you to work with us. But there are just some instances where it doesn’t make sense to go with a developer. 

See below for a quick guide to help you with this question.

You Should Totally Develop In-House If�?/b>

• You have excellent project managers. Knowing all of the possible options is crucial to the success of your app. People often underestimate the importance of the system definition specifications and system design specifications. It’s a foundation with which you can properly build your app. If your project managers can properly assess the needs of your company and plan out a project, your app will be off to an excellent start.
• You have developers with the proper skill sets and time. Ultimately, your app is limited by the expertise of your team. There is often a big gap between the idea and the execution. If you have programmers who can execute the idea in the proper framework on the preferred platform, developing in house might be an excellent option. If you don’t, hiring the developers to execute your vision is also an option, though that begins to push the investment price up. Couple that with training and helping the employee acclimate to your company, and it can be a headache.

You Should Totally Work With a Developer If�?/b>

• You don’t have any in-house developers: Well, duh. You’re probably going to need to hire someone. Unless you have a really fast learner who also happens want to work for 70 hours a week for the next six months.
• You need help with the first step: You might have some great project managers, but many of them don’t know where to start with an app. That’s okay! A developer can come in, assess your needs, develop a timeline, give you the blueprint and send you on your merry way.
• You like your team but they can’t do it all: We get this all the time. A company has a great start on a solution but they are missing some crucial components. Bring a developer in, we’ll help where it’s needed and we’ll part ways when it’s done.
• Your team simply doesn’t have time to take on one more big project: You can’t imagine how common this is. Simply put: internal teams are often already too buried to take on a large project or manage it effectively. Partnering with an outside developer can get a project executed quickly, and there are plenty of options to ensure that you still have whatever control over the process and outcome you desire.

If you haven’t been able to tell yet, it all comes down to talent. Even if your team hasn’t made an app yet, but you trust their ability, developing in-house is a possibility. But if you have any doubts, hiring a developer is a much safer bet.

---

Want To Work With A Developer?

Logic Solutions is a fantastic company to help you realize your mobile or web dreams and grow your business. Let us create the mobile apps, websites, or healthcare solutions that you need to stay on top of the times.

Find your perfect solution

---

---

---

Pierce Courchaine is a marketing coordinator at Logic Solutions. When he’s not in the office, he’s rumbling around the country in a 1996 Honda Civic he lovingly named Martha. Martha’s air conditioning doesn’t work anymore, her power locks failed, her back left window doesn’t open and her 106 horsepower has made for some heart-pounding races against Vespas. For some reason, he’s the only one who can see what’s special about her.

The post When Should You Develop In-House? appeared first on 雷技信息科技（上海）有限公司.

]]>