Skip to main content

Why companies don't launch Mobile/Touch products at same time in Asia ?


This question came recently in our daily meeting and my colleagues were explaining all the benefits of launching Mobile/Touch Products same time in US and in Asia (China, India, Middle East). These are the few points/advantages of introducing products same time in Asia.
  1. Huge Consumer market ( 600 Millions) and is as mature as US.
  2. People love/admire for great products (Apple, Android, Samsung etc)
  3. Duty/Tax free destinations (Dubai etc)
  4. Seems a very potential market for launching products same time.
So why biggies hold off their product for atleast 6 months before they really enter these markets and some people might argue its because of import/export regulations and shipment on the contrary all these products are assembled in Asia and these companies have bigger footprint in these markets.

People directly involved in these decisions are the right person the give us inside but here is my opinion.

  Brand Building 
     Silicon Valley/USA is the best place to Build Brand cheaply i.e. you don't have to pay for expensive celebs to promote your products and the community is so rich (Intellectually) and and strong (opinion) they can tear down or create buzz (Hype) about a product and the rest of the folks will simply follow the buzz,

  Contrarily you don't want to launch something outside Silicon-Valley (USA) coz the buzz created outside will not reach far enough and will not create much consumer confidence.

I guess all the companies wan't to cheaply build the great brands/products first here and then will be in better shape to move to the rest of the markets.


     

Comments

Post a Comment

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more