NAV
<

Overview

MegoHelper is one of the module of MegoGrid. So here I am explaining what MegoHelper is and how it works for an Android App Developer.

Now a days , Mobile Technology is becoming too vast for the ease of the world, keeping the KISS principle (Keep It Short and Simple), Developers are doing their best to make the world Techno Freak. As their time is too precious, Frameworks are being developed to save the time. So, Every developer needs details of their application users, by which they could kept record of each and every brief detail of their user, which he/she could use accordingly.

Now I am sure, Everybody have some questions in their mind, So lets start knowing What, Why and How? about MegOUser.

MegoHelper Demo is app which apply photo effects of camera images and Gallery images.This app is avalable in Google Play and its source code avalable on Github.You can take all refrence of source code and how we integrate a power platform of Mego User as for authentication and backup synching.In this i represent i will guide you how we can integrate Mego User to a App and how this power framework makes Authentication mechnism so simple whether it is login from mechnism from facebook,Google Plus and email and all this finally integrate with our powerfull megogrid Server.

This tutorial is divided into several parts, each focusing on a different aspect of our Mego Grid Demo App. Feel free to read them in any order, but we recommend that you download the source code and refer to it while reading. Some parts of the code were omitted or changed in this tutorial in order to keep it clear and concise, so you may find it useful to keep the full version close at hand.

MegoHelper demo architecture

MegoHelper Demo app contains five main activities: SplashActivity handles the intializes logo delay which around 5 Second,MainActivity shows the effects catagories option whether is from camera and Gallery , PhotoActivity this activity apply different Effects on the images whether it is Capture from Camera or from Gallery,Help it is showing basic help content of app.

Aside from basic functinality we had integrate our MegoGrid Api in differnt section of application

Getting Started

Authorization

To use the MegoHelper SDK first of all you need to authenticate your application/device with our server. So to authenticate your application/device use the Authentication-Layer SDK and call the below mentioned code in your app launcher Activity.

Integrating Authorization SDK in your Android app

Inside the onCreate() method of your SplashActivity configure MegoAuthorizer SDK .

MegoAuthorizer megoAuthorizer = new MegoAuthorizer(SplashActivity.this);
megoAuthorizer.intializeSDK();

Integrating MegoHelper SDK in your Android app

Inside the onCreate() method of your SplashActivity configure MegoHepler SDK .

MegoHelperManager megoHelperManager = new MegoHelperManager(SplashActivity.this);
megoHelperManager.intializeSDK();

Help

Now a day help section is very important for every app it provide a centerlised area for application help and using this any user get help regarding app.Help section explore also some misunderstanding sections of app and provide ease to user and that increase accessiblity to the app.to enable help section in your

In our demo app we use TextView widgets that are defined in the activity_main.xml layout to call history page functionality and is accessible via the options menu in MainActivity, but you can use any of the android widgets. We find the widgets in the onCreate() method of MainActivity to begin history calling flow:

 help_view = (TextView) findViewById(R.id.help_v);

In the code above, an OnClickListener handler is attached to the logout textview that’s identified by the help_view resource. This in turn calls the private onLogoutClick method where we call the logout API function of MeUser:

help_view.setOnClickListener(new OnClickListener() {
            @Override
            public void onClick(View v) }
                try }
                    megoHelperManager.showHelp();

                } catch (MegoHelperException e) }
                    e.printStackTrace();
                } catch (ActivityNotFoundException a) }

                }
            }
        });

Tutorial

As the research says sometime visual content reaches an individual’s brain in a faster and more understandable way than textual information. Or, more accurately, a person’s brain is hardwired to recognize and make sense of visual information more efficiently, which is useful considering that 90 percent of all information that comes to the brain is visual.So to support application help content in the form visual reprenetation we have Tuotorial section in our framework.

In our demo app we use TextView widgets that are defined in the activity_main.xml layout to call history page functionality and is accessible via the options menu in MainActivity, but you can use any of the android widgets. We find the widgets in the onCreate() method of MainActivity to begin history calling flow:

 Tutorial = (TextView) findViewById(R.id.Tutorial);

In the code above, an OnClickListener handler is attached to the logout textview that’s identified by the Tutorial resource. This in turn calls the private onLogoutClick method where we call the logout API function of MeUser:

Tutorial.setOnClickListener(new OnClickListener() }

            @Override
            public void onClick(View v) }

                try }
                    megoHelperManager.showTutorial();
                } catch (MegoHelperException e) }
                    e.printStackTrace();
                } catch (ActivityNotFoundException a) }
                }

            }
        });

FAQ

Frequently asked question are common listed question and answer that are supposed to be confusing point of app.So by enabling FAQ in their app developer would able to set various question in their application

In our demo app we use TextView widgets that are defined in the activity_main.xml layout to call history page functionality and is accessible via the options menu in MainActivity, but you can use any of the android widgets. We find the widgets in the onCreate() method of MainActivity to begin history calling flow:

 faq = (TextView) findViewById(R.id.faq);

In the code above, an OnClickListener handler is attached to the logout textview that’s identified by the faq resource. This in turn calls the private onLogoutClick method where we call the logout API function of MeUser:

faq.setOnClickListener(new OnClickListener() }

            @Override
            public void onClick(View v) }

                try }
                    megoHelperManager.showFAQ();
                } catch (MegoHelperException e) }
                    e.printStackTrace();
                } catch (ActivityNotFoundException e) }
                }
            }
        });

FeedBack

Every software is build for solving a problem of humans and to reduce human effort by implemented digitalisation in the form of software.So any software is not becomes perfect untill it moves in multiple iteration of feedback and there it comes feedback.Today in application world whenever a application is delivered to anyone the developer should definately expect a feed back from him.feedback is very important part of any application because due to feedback of an app developer is able to extend for services to the app and it is very important for future of app.

In our demo app we use TextView widgets that are defined in the activity_main.xml layout to call history page functionality and is accessible via the options menu in MainActivity, but you can use any of the android widgets. We find the widgets in the onCreate() method of MainActivity to begin history calling flow:

 feedback = (TextView) findViewById(R.id.feedback);

In the code above, an OnClickListener handler is attached to the logout textview that’s identified by the feedback resource. This in turn calls the private onLogoutClick method where we call the logout API function of MeUser:

feedback.setOnClickListener(new OnClickListener() }

            @Override
            public void onClick(View v) }
                try }
                    megoHelperManager.showFeedback();
                } catch (MegoHelperException e) }
                    e.printStackTrace();
                    
                } catch (ActivityNotFoundException a) }
                }
            }
        });

RateUs

Whenever any application is delivered to app store every developer is waiting for Rating.Positive rating makes application popular among the store.So provide positive rating to app store and negative rating to your dashboard

In our demo app we use TextView widgets that are defined in the activity_main.xml layout to call history page functionality and is accessible via the options menu in MainActivity, but you can use any of the android widgets. We find the widgets in the onCreate() method of MainActivity to begin history calling flow:

 ratingreview = (TextView) findViewById(R.id.ratingreview);

In the code above, an OnClickListener handler is attached to the logout textview that’s identified by the ratingreview resource. This in turn calls the private onLogoutClick method where we call the logout API function of MeUser:

ratingreview.setOnClickListener(new OnClickListener() }

            @Override
            public void onClick(View v) }


                try }
                    megoHelperManager.showrating();
                } catch (MegoHelperException e) }
                    e.printStackTrace();
                 
                } catch (ActivityNotFoundException a) }

                }
            }
        });




© 2015-2016 Megogrid Inc. / Term of service / Licenses / Privacy Policy 913 N Market Street Suite 200 Wilmington DE 19801 USA