I am using expo 39 SDK is it possible to integrate clever tap notif without ejecting it
In theory, you should be able to do this... However in reality, it may be a bit more complicated. Clovertap is quite specific in terms of exact compatibility without ejecting. It seems that there is little documentation out (at the time of this initial post) for compatibility and use cases between the two systems.
Depending on your underlying problem, another solution may actually be to switch over to FirebaseCloudMessaging.
With that said, lets address the asked problem.
You will probably need to dive into the documentation and attempt code to find out the nitty gritty. I would recommend starting with the push notification documentation:
https://docs.expo.io/push-notifications/overview/
https://docs.clevertap.com/docs/push
Related
I'm developing an app in which i'll play music which is synced your current walking or running pace. In order to do so i have tried using a pedometer input from expo, however this isn't working too great. Input of the pedometer is delayed and is therefore hard to fix. Is there a "better" way to get pedometer inputs in react native more reliably? Otherwise i could opt for trying to guess a walking / running pace by deeming how fast the user is travelling with google maps or similar.
How would you approach my problem?
I would drop expo. With expo you will be limited in the capabilities of your app, meaning you won't be able to add 3rd party native libraries to your app. These are what you are looking for to get the data you want. A quick google search found this, and I guarantee there are many other similar packages if this doesn't quite fit your needs: https://github.com/mathieudutour/react-native-pedometer
Once you drop expo, a world of possibilities will open up to you, but if you are unable to drop expo ... Not being an expo expert, I'm not sure what can be done to get better data. Depending on what you have made so far, dropping expo may be a difficult experience. Either way, good luck.
Cn1 offers a push seamless integration using its own servers that takes care of forwarding to fcm/apple servers for you. This works great, but requires a PRO subscription ($79/month)
I love cn1 and want to support the project as much as I can. I want to include push in my app dev, don't mind going through the extra pain of going native and don't find that adding push in my app dev is worth $79/month
I know that part of that cost surely must go towards maintaining the push servers, so I won't ask for something like bringing cn1 push to basic subscriptions which would be unfair
My point is, can native push be done in cn1. Thanks
It isn't actively blocked it's just unsupported due to the complexity in unifying the vastly different behaviors between iOS and Android. E.g. the parse cn1lib supports its own push which isn't based on our implementation.
I can't tell you how well that works.
It's not something we officially support but it's not something we prohibit.
I'm working on an app written in Codename One together with the parse4cn1 library, the combination of which is a real pleasure to use. However, I need support for a few things in parse4cn1 that are not implemented, most importantly ACL and was wondering if Chidiebere has any hints on how to do this (e.g. how did you implement parse4cn1 yourself - from scratch or copying the open source Parse SDK for Android)? If I manage to do something of a decent quality I will try to share back. Thanks in advance
I never got around implementing ACLs (it's still on the TODO list). parse4cn1's interface closes resembles the Parse Android SDK interface and I'll like it to stay that way for convenience. In this case, the interface of interest would be the ParseACL which is documented here.
The actual implementation will need to be done via REST API calls.
Things to bear in mind:
We use the Android SDK API simply for defining methods and signatures for the corresponding class in ParseACL but do not use the SDKs for anything can be be done via REST.
By design, any calls requiring the master key will not be supported in parse4cn1 due to security considerations. If really needed, the functionality should be exposed via server-side cloud code.
Pull requests without unit tests for the added functionality or breaking existing tests will be rejected.
See also the Contributions section of the parse4cn1 github repo.
Good luck with your implementation and I hope to see a PR from you soon ;)
It was implemented from a Java port on top of the REST API's here but was later modified to use the SDK's to allow things like push (which are now no longer relevant).
In the past I just contributed pull a request to the project to get the fixes/features I needed. It was really easy to work with and compile.
I have been looking at the various Meanstack frameworks out on the net - and whilst impressed with what they achieve I have one serious concern - the number of files used in a typical stack - meanstack.js uses over 15000 files whilst the bmean example has a modest 1900 in comparison.
The question I am asking myself is would I be happy to put my trust is such a system from a production view point - what happens when something goes wrong how easy is it going to be to find the answer? You can almost bet that when your most important customer logs on it is going to go haywire. Also what happens when Angular version 2 comes along it could require a complete rewrite but by then the stack your using has been customised and difficult to change?
Am I getting over concerned about the technology - my intended approach is to strip the client side code out of the bmean example and rewrite it with my own - at least that way I know (and control) what goes on in the client. Do you think this is the correct way to proceed?
With most systems there is a bit of preparation required before going to production. The same is true with mean.io (using multiple cpu's, improved aggregation, caching, etc etc)
The large number of files is essentially a product of the way npm handles dependencies. Each module is able to define independent versions of the same dependencies thus creating a bit of bloat but at the same time allowing a lot of flexability in nodejs code.
We currently have a number of mean.io projects in production phase and have been very happy with performance and the overall experience.
New releases of the project are scheduled every couple of months, upgrading should not be too much of a problem if you use the package system correctly.
Issues with the project are handled and managed through github issues additional support can be found on our irc (freenode #mean_io) channel as well as on facebook.
For commercial support have a look at the support page
I was starting to write a multi-Map JS library, but I see that Mapstraction does that exactly..
I really would like to use Maptraction but it looks a little old (The commit's on GITHUB) (Not a issue if it is still "supported"), also The tutorial page, the Maps do not show up in my browsers.
Any input is highly appreciated.
Thanks
Kim
Depends what your use case is - if you don't want to be tied in to any one map provider and only need standard features then, yes.
Version 2.1 of Mapstraction is currently being prepared (on the release-2.1 branch) which brings some improvements in behavioural consistency across the providers.
Because of the nature of the library development isn't continuous and tends to be reactive to changes in the underlying providers or issues being raised. That said the community is fairly active and you can sign up to the mailing list via the site.