I am playing around with the review actions, more specifically with the movie review example. Suppose that you want to review different characteristics of the movie, like sound, special fx, etc. Is there any way to do that?
No, the ReviewAction can only be used with quick single-rating reviews. The user experience for more complex reviews inside a small dropdown in Gmail will be poor, so those should be handled on a dedicated site.
Related
Does anyone have experience implementing multiple subscriptions model for an app? I wasn't able to find proper documentation about this topic. The most common way to create in-app subscription model is one-subscription per one-user. But I want to offer one-subscription per one-item(in my app). This means that users can create multiple subscriptions if they want to subscribe to multiple items. Each item is functionally the same.
For example, If the app is a pet location tracker and wants to track both pet A and B, the user has to subscribe to each A and B respectively. It means a total of 2 subscriptions.
Please explain it to me.
Thanks.
Never thought about such a use case, but for iOS you can create multiple subscriptions. So you could create a subscription PetA, PetB, PetC and so on. But, I think you asked for a more dynamic approach where you create a Pet subscription and the user can buy as much as he likes. As far as I know this isn't possible.
A different approach would be to create a subscription hierarchy: onePet, twoPets, threePets and so one. Your user can then up or down grade between those subs depending on how many pets he wants to track. Could get messy if you also want to offer different durations.
A third approach could be to use consumable IAPs. These can be purchased as often as the user likes, but have the disadvantage that you need to keep track of the validity period on your own and they can't be synced automatically between multiple devices.
For your pet example I would go for the second approach and offer a onePet, twoPet, threePet and a unlimitPet subscription. This is the most maintainable approach as long as you do not offer endless duration variations. Also this gets synced automatically with all devices of the user and if you like you can also support family sharing.
I have a question for a project I am working on. I am working on a RoR project in which a site is selling a single type of item, a book. The person I am creating this for does not want to deal with users creating user account to check out as the sales season is very short for this product, the purchases are done once per year, and the site only sells a single item.
I am wondering if there is something wrong with the implementation I am thinking of. What I was envisioning was a single database class called Orders. visitors to the site would simple fill out an order form with payment details through stripe and click submit. If they payment clears, the order with all the Orders information would be persisted to the DB. If the payment fails then it is not persisted and the relevant error information is displayed in using flash.
I suppose the meat of my question is; is there anything inherently 'wrong' about implementing this model without a users class and just having visitors to the site place orders?
I am a fairly new developer and this is my first big project so any feedback is appreciated!
If your requirements say that it is okay, then it is okay, if your requirements say it is not okay, then it is not okay.
There's not more to say, since only you know what your requirements are.
I have an SAAS online product (it affects people with twitter accounts, suggests people\pages to follow based on your previous interests).
I would like to add the option to schedule tweets (an ability to not send a tweet now, but schedule it for later, so a person can schedule several tweets at a time and it will be send out during the week) to my product, because I have noticed a lot of people pay for it.
How can I add this functionality to my product, in a way that will be competitive and people will use it?
I would greatly appreciate any help with this, since it's a key for my product's growth.
Thanks!
We've implemented user-level tracking using the documentation https://support.google.com/analytics/answer/3123666?hl=en, including creating specific reporting views User Behavior and Monitor User. Despite this, we cannot see any views in GA which display the individual user ids. How to do this? I'd like to be able to answer these kinds of questions:
Which individual users are heaviest users of app, are what are
specific flows, events that they are doing? What is their behavior
like?
Which individuals are lightest users of app?
Which users have never used certain features?
Thanks!
What you are describing comes very close violating the Google Analytics TOS. You need to ensure that you do not send any Personally identifiable information to Google Analytics.
The user id feature is more practically intended to understand aggregate user behavior and unify cross device sessions. If you rephrased your query to not get at individual users but groups you could easily answer some of your questions.
Which user groups are heaviest users of the application? create a segment which contains your definition for a user which makes heavy use of your application and query for the specific pages that segment visits.
I'd like to program an app which essentially has the same functionality, but with different personalization at the icon level. For instance, the app essentially would have information and communication functionality for a particular business, but I'd like to have the icon/name in front reflect the specific business name. So in other words, the app would let you do things like browse merchandise and place orders, but for two different clients one would say "Home Depot" and the other would be "Loews" in the icon/name.
In the end, I'm customizing the "storefront" to the client, but the backend is pretty much the same in terms of functionality.
Is there any way to do this programatically? I suppose I could submit different apps to Apple, but given that the code would be essentially the same, wouldn't it get rejected for similar functionality?