• User can enable/disable tracking in Settings
• Create a new site on demo.piwik.org
• We ask the user whether he wants to enable / disable tracking on first start (after update/install)
• Create a tracker.js for Piwik Mobile
• Use tracker.js in Piwik Mobile to track views, exceptions, etc.

When clicking on a row (Custom var name) Piwik mobile would show a subtable with values (custom var values) Requested in: http://forum.piwik.org/read.php?2,76375

Piwik Mobile requirements:

• Is Piwik Mobile already able to display a subtable in the same screen?
• Or would Piwik Mobile reload the screen to display only the Custom var values after clicking on a Custom var name? In this case, the "swipe / back" gesture would come back to the previous "Custom variable names" report.

Both solutions would be fine IMO... whatever is easiest/best could be done?

There are also "Piwik core" requirements to make this feature work:

• Piwik Metadata API also returns which API to call when a row is clicked eg. CustomVariables.getCustomVariablesValuesFromNameId

• Piwik metadata should support the API call CustomVariables.getCustomVariablesValuesFromNameId currently unsupported

  Then piwik mobile would call metadata API for this API method which would return the whole report for the row clicked, as a standard Piwik report

Any feedback please post a comment!

Create an iPad specific layout by using a SplitWindow (http://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.iPad.SplitWindow-object ). No Swipe to right, instead open Windows in a modal window or in Popovers (http://developer.appcelerator.com/apidoc/mobile/latest/Titanium.UI.iPad.Popover-object )

We have to refactor the app a bit therefore. Currently, there is always only one active window. All events are fired in thePiwik.UI.currentWindow context currently. Now we have multiple active windows at the same time and we have to make sure that events are fired in the correct context.

I can't login to my piwik instance using Piwik Mobile app default login page. The error message says: "You can't access this resource as it requires an View access for at least one website." The error is thrown immediately after login. On the server, there is one user (me, superadmin) and one page.

However! When I go to "Try it > Accounts > Add new account," using the very same url, login and password, it works and I can browse my page statistics.

Environment:

• app version: "2.0.1 - 3.2.0 543fc64"
• app platform: "iPhone OS 7.1.2 iPhone6,2 (en)"
• piwik version: 2.4.1
• installed on intranet, accessed on HTTP via VPN

hi,

i tried a lot of time, i can't not login via piwik mobile.

but it works when i use the safari to access the login page.

please tell me how to fix it.

hardware:iphone4 OS:iOS 4.2.1

The user should be able to view all columns of the report, to see Conversion rate, Revenue and Bounce rate per entry.

Maybe we add an event listener to the title of the statistic list. The title is the blue label containing for example the text "Unique Pageviews" or "Visits". As soon as the user clicks the label we'll open an Option Dialog where the user is able to select the appropriate? I think there is not really enough space in the headline for another icon.

Another question is: shall we save this selection in a session and use this selection preferably (if the selected statistic supports this)?

Android: Dependent on this issue: https://jira.appcelerator.org/browse/TIMOB-17948 iOS: Not sure whether it already works here or not. If not it might automatically work by setting a TLS version: http://docs.appcelerator.com/titanium/3.0/#!/api/Titanium.Network.HTTPClient-method-setTlsVersion not sure re any other drawbacks etc

In the last version of Android market of piwik mobile, I don't have image, neither sparkling. All graph, small image (as image used for navigator) are absent.

So I have a text only version of piwik. :-)

In Piwik 0.8, a new powerful API was release: metadata API.

The Metadata API is documented in the (new) doc page at: http://dev.piwik.org/trac/wiki/API/Metadata

The Metadata API is used to

• get the list of all reports (category, names, API methods to call, column names, etc.) for all Piwik API reports.
• get a specific API report data set

The Piwik Mobile would therefore not have anything hard coded (list of reports, etc.) as it would simply call the Metadata API once, cache it for the given idSite/date/period.

Then when a specific report is clicked in the Mobile UI, the API.getProcessedReport would return all data ready to be displayed in the Mobile Client.

Let me know if this makes sense.

The big advantage is that, when in the future new reports are released in Piwik, the Mobile client will automatically display these reports (translated, etc.). This should also simplify the code and make maintenance easier.

This Metadata API is currently used to build the PDF UIs and generate PDF reports. It will also be used for the Custom Alerts plugin.

Let me know if you have any question

Add/Edit/Manage Accounts doesn't look that good at the moment. Optimize the screen to look a bit more native. Also add an advice how to delete an account on iOS.

Hey there,

I have Matomo instances running, both with 2FA enabled accounts. When I try to add the second server to Matomo Mobile 2 on iOS, it results in the following error:

Having the first server with 2FA enabled and the second without 2FA, then it works flawlessly.

When it comes to the mobile version, the first thing I realized is that you can only connect with ONE Matomo Dashboard at a time.

It would be a great extension of the mobile app (but also the web version on-premise) if you could register multiple servers that have Matomo on-premise and then switch between them in the app on the fly. Because in a professional environment, you can easily have multiple client servers and multiple Matomo Dashboards that you have to administer.

I appreciate your consideration, and keep up the great work!

Cheers!

A user writes: Question: What is the feature you are missing the most in Matomo and why? Answer: " a confirmation box before signing out. It is easy accidentally signing out when using the web-app on e.g. an ipad or iphone"

On the latest iOS version, when opening the Visits Log, after going back a few pages by pressing the „Previous“ button, entries get displayed on top of each other, making them impossible to read.