October 2015 -

Edelweiss Mobile Trading App gains 4.2 ratings from 47,000 downloads

Posted by | blog | No Comments

Edelweiss Broking, one of the leading stock brokers in India, has always been a frontline adapter of state-of-the-art technology to stay ahead of their competition. They envision their business with technology as a tool to drive growth, increase productivity and to enhance customer experience. Their IT strategy predominantly focuses on business objectives through technology innovation.

EdelweissThe Edelweiss Mobile Trader (EMT) proved to be a good platform to engage customers and drive business. As a strategic decision, they decided to completely revamp their existing EMT with added features and better experience. The vision became real when EMT 3.0 was recently released for Android and iOS smartphone platforms. The migration from existing EMT was seamless and it received an overwhelming response among its users with more than 47,000 downloads and 4.2/5 ratings in app stores.

Market Simplified (MSF) is happy and proud to partner with Edelweiss as Mobility Partner. As a mobility partner, MSF Experience Engineered, Designed and Developed EMT 3.0. The app is loaded with tons of features and following are a few of them to be highlighted.

  • Real-time quote streaming across the application.
  • Dashboard with account summary, open positions and holdings details.
  • Customizable watchlist to list and monitor stocks. It also automatically creates watchlist based on user’s holdings and positions.
  • Live streaming intra-day charts.
  • Historic charts with 23 inline and outline technical indicators to assist professional traders.
  • News and Event calendar to keep the traders informed on market happenings.
  • Simplified trade, execute any trade in 3 simple steps.
  • One step login, simplified and secure login process.

Promotional Video of Edelweiss Mobile Trader 3.0

For more details, write to us at info@marketsimplified.com

About Edelweiss Broking Ltd: Edelweiss is one of India’s leading diversified investment destinations, which helps you trade the in stock market and make investments across multiple asset classes like Equity, F&O, Currency Derivatives, Mutual Funds and Fixed Income products.

About Market Simplified: Market Simplified is a thought leader in handcrafting custom solutions by continuously innovating and simplifying finance. We have maximized the revenues of industry leaders like OptionsXpress (Charles Schwab), Currenex (State Street), MB Trading, Maybank Kim Eng, Kotak Mahindra Bank and National Stock Exchange of India by providing enhanced and sustained user engagement through Experience Engineering.

About The Author: Gokoulane Ravi is a foodie, technology enthusiast and a developer turned marketer with more than 5 years of experience in the space of mobility. When he is not working, he likes to read, write, run and cycle.

Avoiding the pitfalls – Enterprise Mobile Application Development

Posted by | blog | No Comments

Event: CSI IT 2020, IIT Mumbai

Not mobile first.. Think first !

A lot gets written about the new wave of enterprise mobile application development. Platforms, Tools, Frameworks and Magic Wands..(ok.. i made that up) not a day goes without breaking news in these areas. The success & ROI of a few enterprise mobile initiatives gets widely reported while many failures go unnoticed.

This information gap has led many enterprises to take the plunge without adequately planning to mitigate the risks and thereby failing to meet desired outcomes.

Lured by the potential , trapped by the challenges. They take a pitfall !

Definition : pitfall ‘A hidden , not easily recognized danger ‘

I was invited to speak on this topic based on my experience and this article is a written form of the session. I have purposely steered clear of technical details , that i will reserve for a followup article.

#Everything starts with a set of tall requirements + high expectations + #1 priority list

If you are ever asked to do an RCA (Root Cause Analysis ) — Please do it here

#Most mobile projects fail for the exact same reasons as any other project

Only difference being that mobile is 10X more complex because of its nature..

 Avoiding the pitfalls

I have tried to focus on the common pitfalls and how to avoid them. For the sake of current trends in title publishing let me call it “The 4C’s” for a better recall

  1. Clarity you have
  2. Choices you make
  3. Control you show
  4. Change you manage

Clarity you have

Understand mobile technology constraints
SmartPhones, Tablets, Phablets comes in all shapes and forms, Display, Memory, Network, Capabilities, Storage, Associated App Store rules, UX Guidelines etc –Get a clear understanding of your type of user and their environment, build applications for them.

Educate stakeholders
Unlimited Opinions ! Everyone has an opinion when it comes to mobile. They feel they should be part of the change. Listen, Filter, Prioritize, Test Feasibility, Plan

Prepare for surprises
Before you finish you start again – Mobile ecosystem changes every 3, 6, 9 months with major changes every year – This is not an exception this is the norm, prepare yourself, your teams and stakeholders to embrace change

Choices you make

Experience Vs Management
Technology is all about choices, choosing what is right depends on what problem you are trying to solve and how. Make careful assessments of choices offered, choose one that fits your unique needs.

If experience is foremost aka. great UX/UI, Fluid, High Performance, Secure application adopt native development but if manageability tops your list you will have to be ready to give up some experience . I am yet to see tools that offer both but the gap is fast closing. Approaches vary between Native, Pure HTML5, Cross Platform Natives & Runtimes and Hybrid ..more on this in my next article.

Be cognizant of the resources you have in terms of Budgets, Skilled People, Timelines and plan with them in mind. A possible approach is to have the big picture in mind and work out a strategy with a roadmap to get there in small steps.

Existing Data Sources , Formats, Availability
Mobility data needs or different , its context – Your readiness factor in going mobile needs to be evaluated first. In my experience not all functions within an enterprise is ready or in most cases not ready to meet the real expectations from the mobile project.

Data needs to be transformed to meet different context and use cases. It is advisable to spend some time internally to identify data sources, formats , its relevance to context and the availability / access mechanisms.

Control you show

Requirements keeps coming, changing and taking new forms left uncontrolled –Not having process in place to control can freak you and the project.

Mobile projects give high visibility to stakeholders involved. These are early days so there is general excitement in the air to add on new things, some things that they see, hear or to please their sponsors who saw something in a recent business travel. User Experience and Interfaces are the most subjective areas and the greatest areas of debate.

While ideas should be welcome, it is advised to put in proper curation process for ideas so that teams can test its feasibility and value.

The fear of failure is human nature. Its our primal instinct. Mobile projects being highly visible in the Enterprise, especially the customer facing applications , the fear factor with managers are very high. The constant change in the ecosystem and the possibility of the application breaking with the next best update cannot be brushed aside. The service provider, internal IT teams and business have to work together to identify and take proactive measures. Some control is with us, some with the app store . Being aware is a possible solution

Change you manage

Requirement Vs Impact
Every new requirement has a double impact. Blindly translating requests into requirements is one of the mistakes we as service providers do. Clients are typically unaware unless impacts are carefully articulated. Time and resources should be set aside in parallel to evaluate impact early and not left to emerge as surprises later

Experiment – A / B , 80 :20
Not all things need to be accomplished day one. A / B testing is one form of experimenting to identify what makes your app stick and create the engagement you strived for. Remember 80:20 rule, spend time in identifying the impactful functions and ways people use them. Make decisions based on data evidence and not on personal biases

Being aware of the 4C’s and working with vendors as partners can lead to better outcomes in mobile projects. In my next article i will cover some details on Approach to mobile development and magic wands for real !


Viral Effects – Why some things catch on like wildfire

Posted by | blog | No Comments

Have you ever wondered why some things fail, while others catch on? Leaving us head scratching? I did. This lead me to read a great book Contagious “Why things catch on” by Jonah Berger.

Applying the learning I have picked some popular digital content we have come to see, like / dislike yet talk / share and therefore played an active part for it to catch on and spread..like wildfire

Contagious discusses about the STEPPS principle, which is

  1. Social Currency – We share things that make us look good
  2. Triggers – Top of Mind, Top Of Tongue
  3. Emotion – When we care about something , we share
  4. Public – Built to show, built to grow – better visible products
  5. Practical Value – News & Information we can use
  6. Story – The packaging of core content

Popular Digital Content

Why this Kolaveri – 82,686, 017 Views, A tamil song that broke youtube records

Charlie bit my finger, 748,929,88 Views, A cute video to show your infants

Gangnam Style , 2,054,131,618 Views, I don’t even have to say about this

Meaningless in a world of meaningful songs, Can’t get it out of the head phenom, Easy to Humm & Rhyming, A new language Tanglish – Tamil + English, Duplication by public / groups / popular artists, Local Youth dialect/ slang, Appeals to local youth emotions of a breakup lyrically, Critics Comments, Leaked video speculation

The unique horse riding dance step, the catchy tune ( i bet we cannot remember or sing 3 lines of this song), Celebrity Endorsement of moves, Kids pick this up and show off (adding to parental showoff) , the comical characters in video, we got to know that gangnam is an upmarket district in korea, this became a victory dance

Very Cute, makes my kid eats his food all the time (practical value), Freshness though an old video, Built in sharing value, Laughter & Happiness every time you see it

Now think about products like Facebook, Evernote, Whatsapp, Candy Crush, Google search, Twitter, Snapchat .. think about why a restaurant recall is because of it’s one dish, why do some trailers make you want to watch the movie first day / first show !

What we see here is they are all share something in common, they all have something we talk about . There is nothing more powerful in marketing than WOMO “Word of Mouth”. Things catch on when one or many of these attributes work. There are numerous examples of this in this world today. Yo ! the app anyone ?

attention is the scarce commodity in today’s world

Understanding the product/service/content we create , will help us question its purpose, questioning helps us see what might get attention. The book has some real great examples, pick your digital copy today , apply the principles discussed in the next product or content you create and share what worked.

IT Depends !

Posted by | blog | No Comments

Following up on my previous article that touched upon human aspects in managing mobile projects, I am going to focus this article a level below on the tools & approaches that’s of critical consideration and a topic for immense debate.

As a solution provider i encounter these questions quite often.. Are we right in standardizing on this tool ? Is this tool the best? I know a friend who used this and did the project in 50% of the time. Is it possible? I read an article that says i can save 80% of my development costs ! Is it true? While you answer these remind yourself that “We need to be the Top 5 in our category in the app store , no matter what ”

The questions they are referring to are mostly to do with the development approach along with the usage of a cross platform toolkit aka the magic wand reference in my earlier article

The only answer I always give is “IT Depends” as with everything in technology..whether we buy a smartphone or consumer electronics .. our needs are different

Let’s understand the factors to consider

  • The development approach largely depends on the outcome you expect, management , costs , user experience, quality & release cycles you need
  • Building native means you have complete control and the resultant experience is what you have come to expect – like the smooth games you play. Here the No pain , No gain philosophy holds true.
  • Most Cross Platform toolkits provide enterprise connectors which help you get your data sources ready either on their own or with a BaaS platform partner
  • Cross Platform tools, provide an abstraction layer and the approaches vary by their design architecture , each have their own limitations like app sizes, runtime dependencies, common look and feel across, performance etc. Here i flip the philosophy to Less Pain, Less Gain
  • Their costs vary per app / deployment / connectors and other enterprise management components
  • Long term manageability and internalizing skillsets is a good factor to consider
  • What works for one, may not work for you – Your needs are unique assess them and articulate early to your development partners
  • The web browser you use in your mobile is not the same as in your desktop. The Web runtimes in mobile vary, so bundling or wrapping HTML5 content should be done with understanding of the target platform
  • These tools are like magic, in the surface it will give you an illusion effect that it can solve all your problems all the ways you want it to but as in magic it can fade away quite fast – If their use is not qualified by you
  • If your needs are simple and straight, CPT will give you the best value and a right path to take. The issue comes when you have a place high demand on experience and performance that will require to push these tools to the limits

So whats the advice here ?

  • Clearly outline your requirements and get a prototype application built. Test key expectations and assumptions here.
  • Understand your target audience and their aspirations.
  • Look at your overall enterprise strategy and choose the best approach that fits.
  • Get your enterprise plumbing in place , a layer that unifies and connects all your backend data sources.
  • Train your internal staff to manage risks and support extensions

Example : The case for retail financial applications

Retail financial applications are a different breed than any other type of applications i have built. The apps handle real time data feeds, perform data visualizations ( think beyond the primitive chart patterns), fast seamless manipulation of data on screen, custom security requirements and uncompromisable performance. These factors have naturally lead us to develop natively for each platform. We also continue exploring / experimenting with the tools and approaches as technology is dynamic and our future depends on making the right choices for our clients.

At Market Simplified we are engineering experiences for our financial clients across the globe, we are trying to meet special requirements always with a fine detailing on what the retail / customer facing applications category users demand . We always ask

How long can financial applications be boring ?

powered by
Welcome! Let me know how I can help you!