Recherche avancée

Sur d’autres sites (6909)

• How to make Matomo GDPR compliant in 12 steps

  3 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

  The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

  The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

  We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

  The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

  As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

  If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

  1 – Awareness

  Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

  2 – Information you hold

  List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

  3 – Communicating privacy information

  a – Add a privacy notice

  Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

  b – Add Matomo to your privacy policy page

  Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

  4 – Individuals’ rights

  Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

  5 – Subject access requests

  Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

  6 – Lawful basis for processing personal data

  There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

  7 – Consent

  Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
  We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

  8 – Children

  If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

  9 – Data breaches

  As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

  10 – Data Protection by Design and Data Protection Impact Assessments

  Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

  11 – Data Protection Officers

  If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

  12 – International

  Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
  Note : our Matomo cloud infrastructure is based in France.

  That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

  The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.

• How to measure the performance of a newsletter (or any email) with Matomo

  19 décembre 2017, par InnoCraft

  To be able to grow your business, it is crucial to track all your marketing efforts. This includes all newsletters and emails that you share with people outside of your business. Otherwise, you won’t be able to know which of your daily efforts are yielding results.

  Are you wondering if it is possible to track the performance of an emailing campaign in Matomo (Piwik) efficiently ? Would you like to know if it is technically easy ? No worries, here is a “How to” tutorial showing you how easily you can track an emailing in Matomo properly.

  Different tracking levels for different needs

  There are many things that you may be interested to track, for example :

  

  1. How many users opened your email
  2. How many users interacted with the links in your email
  3. How many users interacted on your website through your email

  Let’s have a look at each of these levels.

  Step 1 – Tracking email and newsletter openings in Matomo

  Tracking email openings requires to add an HTML code to your newsletter. It works through what we call a tracking pixel, a tiny image of 1×1 that is transparent so the user will not be able to see it.
  In order to install it, here is an example of what this code looks like :

  <img src="https://piwik.example.com/piwik.php?idsite=YOUR_PIWIK_WEBSITE_ID&rec=1&bots=1&url=https%3A%2F%2Fexample.com%2Femail-opened%2Fnewsletter_XYZ&action_name=Email%20opened&_rcn=internal%20email%20name&_rck=newsletter_XYZ" style="border:0;” alt="" />

  The Matomo tracking pixel explained

  The above URL is composed of the following URL parameters which are part of our Tracking API :

  • idsite : Corresponds to the ID of the website you would like to track.
  • rec : You need to have rec=1 in order for the request to be actually recorded.
  • bots : Set it to 1 to include all the connections made to this request, bots included.
  • url : corresponds to the URL you would like to display in Matomo (Piwik) every time the email is opened.
  • action_name : This is the page name you would like to be tracked when the email is opened.
  • _rcn : The name you would like to give to your campaign.
  • _rck : The keyword you may like to use in order to summarize the content of your newsletter.

  You may have noticed some special characters here such as “%20”, “%2F”. That’s because the URL is encoded. We strongly recommend you to do so in order for your tracking not to break. Many tools are available on the web in order to encode your URLs such as https://www.urlencoder.org/.

  If you would like to access the previous tracking code easily, keep in mind that you can always find the tracking code generator within the “Matomo admin panel → Tracking code” :

  

  You can find more information about it on our guide at : How do I track how many users open and read my newsletter emails (using a pixel / beacon) ?

  As a result, the information will be pushed as following for any user who opens your email :

  

  To not bias your regular page views on your website with newsletter openings, we recommend tracking newsletter openings into a new website.

  Tracking even more data : the user ID example

  You can go deeper in your URL tracking by inserting other parameters such as the user id if you have this information within your emailing database. One of the main benefit of tracking the User ID is to connect data across multiple devices and browsers for a given user.

  You only need to add the following parameter &uid=XXX where XXX equals the dynamic value of the user ID :

  

  Make sure that UID from your emailing provider is the same as the one used on your website in order for your data to be consistent.

  Important note : some email providers are loading email messages by default which results in an opening even if the user did not actually open the email.

  Step 2 – Measure the clicks within your emailing

  Tracking clicks within an email lets you know with which content readers interacted the most. We recommend tracking all links in all your emails as a campaign, whether it is a newsletter, a custom support email, an email invoice, etc. You might be surprised to see which of your emails lead to conversions and if they don’t, try to tweak those emails, so they might in the future.

  Tracking clicks This works thanks to URL campaign tracking. In order to perform this action, you will need to add Matomo (Piwik) URL parameters to all your existing link URLs :

  • Website URL : for example “www.your-website.com”.
  • Campaign name : for example “pk_campaign=emailing”. Represents the name you would like to give to your campaign.
  • Campaign keyword : for example “pk_keyword=name-of-your-article”. Represents the name you would like to give to your content.
  • Campaign source : for example “pk_source=newsletter”. Represents the name of the referrer.
  • Campaign medium : for example “pk_medium=email”. Represents the type of referrer you are using.
  • Campaign content : for example “pk_content=title”. Represents the type of content.

  You can find more information about campaign url tracking in our “Tracking marketing campaigns with Matomo” guide.

  Here is a sample showing you how you can differentiate some links in a newsletter, all pointing to the same URL :

  

  Once you have added these URL parameters to each of your link, Matomo (Piwik) will clearly indicate the referrer of this specific campaign when a user clicks on a link in the newsletter and visits your website.

  Important note : if you do not track your campaigns, it will result in a bad interpretation of your data within Matomo (Piwik) as you will get webmail services or direct entries as referrer instead of your newsletter campaign.

  Step 3 – Measure emailing performances on your website

  Thanks to Matomo (Piwik) URL campaign parameters, you can now clearly identify the traffic brought through your emailing. You can now specifically isolate users who come from emails by creating a segment :

  

  Once done, you can either have a look at each user specifically through the visitor log report or analyze it as a whole within the rest of the reports.

  You can even measure your return on investment directly if goals have been defined. In order to know more about how to track goals within Matomo (Piwik).

  Did you like this article ?

  If you enjoyed reading this article, do not hesitate to share it around you. Moreover, if there are any topics you would like to write us about in particular, just drop us an email and we will be more than happy to write about it.

  The post How to measure the performance of a newsletter (or any email) with Matomo appeared first on Analytics Platform - Matomo.

• Build FFmpeg for All Android architecture correctly

  26 octobre 2017, par fthopkins

  I built ffmpeg libraries for all android architecture. But some details are confusing my mind. First of all let me explain step by step how i built.

  • I downloaded latest version of libx264 from
    https://www.videolan.org/developers/x264.html
  • Created and run build_all.sh script (in x264 folder) for creating libs for (almost) all android platforms. Then i got android folder in x264 folder. e.g android/arm android/arm64 android/x86 android/x86_64 in x264 folder.
  • I download the ffmpeg3.3.4 from https://ffmpeg.org/download.html
  • I created 4 copies of ffmpeg3.3.4 folder. Named them with android architectures names.
    Like ffmpeg3.3.4-arm64 ffmpeg3.3.4-arm ffmpeg3.3.4-x86 ffmpeg3.3.4-x86_64
  • Created build_(architecture-name).sh for each platforms of android. Than move each one of 'named'.sh files to the named ffmpeg folders according to their architecture names.
    E.g build_android_x86.sh => ffmpeg3.3.4-x86

  build_android_arm64.sh example

  #!/bin/bash
  
  #Change NDK to your Android NDK location
  
  NDK=$HOME/Android/Sdk/ndk-bundle
  
  PLATFORM=$NDK/platforms/android-21/arch-arm64/
  
  PREBUILT=$NDK/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64
  
  
  
  GENERAL="\
  
  --enable-small \
  
  --enable-cross-compile \
  
  --extra-libs="-lgcc" \
  
  --arch=aarch64 \
  
  --cc=$PREBUILT/bin/aarch64-linux-android-gcc \
  
  --cross-prefix=$PREBUILT/bin/aarch64-linux-android- \
  
  --nm=$PREBUILT/bin/aarch64-linux-android-nm \
  
  --extra-cflags="-I../x264/android/arm64/include" \
  
  --extra-ldflags="-L../x264/android/arm64/lib" "
  
  
  
  MODULES="\
  
  --enable-gpl \
  
  --enable-libx264"
  
  
  
  
  
  
  
  function build_arm64
  
  {
  
    ./configure \
  
    --logfile=conflog.txt \
  
    --target-os=linux \
  
    --prefix=./android/arm64-v8a \
  
    ${GENERAL} \
  
    --sysroot=$PLATFORM \
  
    --extra-cflags="" \
  
    --extra-ldflags="-lx264 -Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
  
    --enable-shared \
  
    --disable-static \
  
    --disable-doc \
  
    --enable-zlib \
  
    ${MODULES}
  
  
  
    make clean
  
    make
  
    make install
  
  }
  
  
  
  build_arm64
  
  
  
  
  
  echo Android ARM64 builds finished

  • Moved all ffmpeg3.3.4-arm64 ffmpeg3.3.4-arm ffmpeg3.3.4-x86 ffmpeg3.3.4-x86_64 folders to the NDK_PATH (C:\Users\MyName\AppData\Local\Android\sdk\ndk-bundle)
  • Put x264 folder at same level of hierarchy with ffmpeg folders
    in (C:\Users\MyName\AppData\Local\Android\sdk\ndk-bundle)
  • Run each of build_android_x86.sh, build_android_x86_64.sh.. scripts one by one in their own ffmpeg folder. Then i got android folders in ffmpeg folders. (created android folders have library folders)
    e.g ffmpeg3.3.4-x86/android/x86/(bin,inlude,lib,share)

  • Created Android.mk files for all created android folders and moved each one of them to android/armName folder. e.g Android.mk => ffmpeg3.3.4-x86/android/x86/

    LOCAL_PATH:= $(call my-dir)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libavcodec
    
    LOCAL_SRC_FILES:= lib/libavcodec-57.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libavformat
    
    LOCAL_SRC_FILES:= lib/libavformat-57.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libswscale
    
    LOCAL_SRC_FILES:= lib/libswscale-4.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libavutil
    
    LOCAL_SRC_FILES:= lib/libavutil-55.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libavfilter
    
    LOCAL_SRC_FILES:= lib/libavfilter-6.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE:= libswresample
    
    LOCAL_SRC_FILES:= lib/libswresample-2.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE := postproc
    
    LOCAL_SRC_FILES := lib/libpostproc-54.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE := avdevice
    
    LOCAL_SRC_FILES := lib/libavdevice-57.so
    
    LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)/include
    
    include $(PREBUILT_SHARED_LIBRARY)

  • Create "arm named" folders e.g x86 x86_4 arm64 arm7 in jni folder of my project (myproject/app/jni/x86, myproject/app/jni/x86_64).

  • Go to ndk path open named ffmpeg folders one by one and copy ffmpeg.c ffmpeg_filter.c ffmpeg_opt.c cmdutils.c files from ffmpeg folders to the "arm named" folders. e.g ffmpeg.c => myproject/app/jni/x86

  • Created Android.mk file in my project.

    LOCAL_PATH := $(call my-dir)
    
    #$(warning $(LOCAL_PATH))
    
    
    
    include $(CLEAR_VARS)
    
    LOCAL_MODULE    := videoEdit
    
    LOCAL_LDLIBS := -llog -ljnigraphics -lz -landroid
    
    LOCAL_CFLAGS := -Wdeprecated-declarations
    
    ANDROID_LIB := -landroid
    
    
    
    $(info $(TARGET_ARCH_ABI))
    
    
    
    ifeq ($(TARGET_ARCH_ABI),armeabi-v7a)
    
        LOCAL_C_INCLUDES:=/Users/MyName/AppData/Local/Android/sdk/ndk-bundle/sources/ffmpeg-3.3.4-armeabi
    
        LOCAL_SRC_FILES :=  videoEdit.c arm7/ffmpeg.c arm7/ffmpeg_filter.c arm7/ffmpeg_opt.c arm7/cmdutils.c
    
        LOCAL_CFLAGS += -lx264 -Wl,--no-merge-exidx-entries
    
    else
    
    
    
        ifeq ($(TARGET_ARCH_ABI),arm64-v8a)
    
                LOCAL_C_INCLUDES:=/Users/MyName/AppData/Local/Android/sdk/ndk-bundle/sources/ffmpeg-3.3.4-arm64-v8a
    
                LOCAL_SRC_FILES :=  videoEdit.c arm64/ffmpeg.c arm64/ffmpeg_filter.c arm64/ffmpeg_opt.c arm64/cmdutils.c
    
                LOCAL_CFLAGS += -funwind-tables -Wl,--no-merge-exidx-entries
    
        else
    
    
    
            ifeq ($(TARGET_ARCH_ABI),x86_64)
    
                   LOCAL_C_INCLUDES:=/Users/MyName/AppData/Local/Android/sdk/ndk-bundle/sources/ffmpeg3.3.4-x86_64
    
                   LOCAL_SRC_FILES :=  videoEdit.c x86_64/ffmpeg.c x86_64/ffmpeg_filter.c x86_64/ffmpeg_opt.c x86_64/cmdutils.c
    
            else
    
                    LOCAL_C_INCLUDES:=/Users/MyName/AppData/Local/Android/sdk/ndk-bundle/sources/ffmpeg3.3.4-x86
    
                    LOCAL_SRC_FILES :=  videoEdit.c x86/ffmpeg.c x86/ffmpeg_filter.c x86/ffmpeg_opt.c x86/cmdutils.c
    
            endif
    
    
    
        endif
    
    
    
    endif
    
    
    
    LOCAL_SHARED_LIBRARIES := libavformat libavcodec libswscale libavutil libswresample libavfilter libavdevice libpostproc
    
    
    
    include $(BUILD_SHARED_LIBRARY)
    
    
    
    ifeq ($(TARGET_ARCH_ABI),armeabi-v7a)
    
    
    
        $(call import-module,ffmpeg-3.3.4-armeabi/android/armeabi-v7a)
    
    
    
    else
    
    
    
        ifeq ($(TARGET_ARCH_ABI),arm64-v8a)
    
                $(call import-module,ffmpeg-3.3.4-arm64-v8a/android/arm64-v8a)
    
        else
    
    
    
            ifeq ($(TARGET_ARCH_ABI),x86_64)
    
                   $(call import-module,ffmpeg3.3.4-x86_64/android/x86_64)
    
            else
    
                $(call import-module,ffmpeg3.3.4-x86/android/i686-diasm)
    
            endif
    
    
    
        endif
    
    
    
    endif

  • Created Application.mk file in my project.

    APP_ABI := armeabi-v7a, arm64-v8a, x86_64, x86
    
    APP_PLATFORM := android-14

  • Created videoEdit.c than run ndk-build build command.

  Built with no error. I can run ffmpeg commands but it takes too much time i think. E.g when i try to run hflip it flips the video with 15 seconds.

  Code example :

  JNIEXPORT jint JNICALL Java_com_name_app_library_VideoEditer_natives_VideoEditer_flipHorizontally
  
  (JNIEnv *env, jclass someclass, jstring inputFile, jstring outFile) {
  
  
  
      int numberOfArgs = 14;
  
  
  
      char** arguments = calloc(numberOfArgs, sizeof(char*));
  
      const char *in, *out;
  
  
  
      in = (*env)->GetStringUTFChars(env, inputFile, 0);
  
      out = (*env)->GetStringUTFChars(env, outFile, 0);
  
  
  
      arguments[0] = "ffmpeg";
  
      arguments[1] = "-i";
  
      arguments[2] = in;
  
      arguments[3] = "-c:v";
  
      arguments[4] = "libx264";
  
      arguments[5] = "-preset";
  
      arguments[6] = "ultrafast";
  
      arguments[7] = "-threads";
  
      arguments[8] = "5";
  
      arguments[9] = "-c:a";
  
      arguments[10] = "copy";
  
      arguments[11] = "-vf";
  
      arguments[12] = "hflip";
  
      arguments[13] = out;
  
  
  
      int i;
  
      for (i = 0; i < numberOfArgs; i++) {
  
          log_message(arguments[i]);
  
      }
  
      log_message("Printed all");
  
  
  
      main(numberOfArgs, arguments);
  
      free(arguments);
  
      (*env)->ReleaseStringUTFChars(env, inputFile, in);
  
      (*env)->ReleaseStringUTFChars(env, outFile, out);
  
  
  
      return 0;
  
  }

  FFmpeg Commands that runs on android, working very fast on emaulator but very slow on real device.

  Also another thing to confusing my mind is output of ./configure command.
  When i open the (e.g) ffmpeg-3.3.4-arm64-v8a folder and run ./configure command in terminal. Output says ARCH   x86 (generic). For all platform output is the same ARCH   x86 (generic).

  Output of ./configure command in ffmpeg-3.3.4-arm64-v8a folder

  install prefix            /usr/local
  
  source path               .
  
  C compiler                gcc
  
  C library                 glibc
  
  ARCH                      x86 (generic)
  
  big-endian                no
  
  runtime cpu detection     yes
  
  yasm                      yes
  
  MMX enabled               yes
  
  MMXEXT enabled            yes
  
  3DNow! enabled            yes
  
  3DNow! extended enabled   yes
  
  SSE enabled               yes
  
  SSSE3 enabled             yes
  
  AESNI enabled             yes
  
  AVX enabled               yes
  
  XOP enabled               yes
  
  FMA3 enabled              yes
  
  FMA4 enabled              yes
  
  i686 features enabled     yes
  
  CMOV is fast              yes
  
  EBX available             yes
  
  EBP available             yes
  
  debug symbols             yes
  
  strip symbols             yes
  
  optimize for size         no
  
  optimizations             yes
  
  static                    yes
  
  shared                    no
  
  postprocessing support    no
  
  network support           yes
  
  threading support         pthreads
  
  safe bitstream reader     yes
  
  texi2html enabled         no
  
  perl enabled              yes
  
  pod2man enabled           yes
  
  makeinfo enabled          no
  
  makeinfo supports HTML    no
  
  
  
  External libraries:
  
  iconv            xlib

  EDIT all of these steps made on ubuntu then moved all folders to the windows. So dont be confuse about paths.

  With all of these steps i want to ask is, is there anything wrong on my steps. Should i follow any other way or not ? Why the ffmpeg is running slower on real device. I am wondering one thing badly, how retrica, snapchat, instagram recording video as mirrored flipping ? Are they flipping after recorded (if they are how are they doing this in a second) or are they recording a video as flipped in run time ? I guess building ffmpeg for android is bit messy and making wrong things is very easy. If you look my steps, questions and give me an advice, i will be much appreciated.